Skip to main content
100%

Gist 11250891

✓ Published0🌍 Public
Aandybak
Last edited Apr 24, 2014
Created on Apr 24, 2014

This example shows a PostgreSQL query plan for a Django ORM query that retrieves inventory events by filtering on stock items associated with a specific item model. The visualization renders the EXPLAIN output as a tree of hash joins and sequential scans, using the `explain` command to expose query execution details. The code includes Python Django model definitions and raw SQL, with the query plan revealing how the database optimizes multiple LEFT OUTER JOINs and subqueries against inventory, booking, purchase, and cross-hire tables.

AI-generated description

Similar vizzes

Loading thumbnail…

Gist 11191339

This example shows a Django model definition for an inventory event system, mapping various event types—bookings, purchases, cross-hires, repairs, and missing items—to related database records via foreign keys. The code uses Django’s `models.ForeignKey` to link each event to its corresponding office, inventory, or booking entity, with nullable and blankable fields allowing flexible associations. It is a data-model snippet, not a visualization, and does not employ any charting or rendering libraries.

Aandybak
75% match
Loading thumbnail…

Gist 033ea14fe76d6ec0e0a7

This example shows three versions of a Django view endpoint that retrieves the lowest stock level for a set of item models tied to a subbooking. The first version is a dense one-liner that queries each item ID individually, while the second and third versions optimize by filtering all item models at once using Django’s ORM `filter(id__in=pks)`. The code relies on Django’s `Response` object, `ItemModel.objects`, and `request.QUERY_PARAMS` to parse incoming query parameters, with each version producing the same dictionary mapping item primary keys to their lowest stock values.

Aandybak
70% match
Loading thumbnail…

Gist 24eed51a3fba9e14760d

This example visualizes a Django data model’s query-set filtering logic as a directed graph, showing how `ItemModelQuerySet` methods such as `consumable`, `tracked`, and `hireable` branch from the base `ItemModelManager`. The graph nodes represent query-set operations and their type-based filter relationships, with edges indicating method chaining. It uses the `PassThroughManager` API to expose custom queryset methods, while the rendering approach likely relies on a JavaScript library like `d3.forceSimulation` for node layout, though the code itself focuses on the Python-side model definitions. The data source is the hardcoded queryset class structure from the gist.

Aandybak
70% match
Loading thumbnail…

Gist 7d3d2123ca922c2ab231

This example demonstrates a code snippet that creates a stock order in a Django-based inventory system. It shows the sequence of operations: instantiating a `PurchaseOrder` with a given supplier, adding a row with the specified quantity, and attaching a hidden arrival event for the creation date and location. The code relies on Django’s object-relational model (`PurchaseOrder.objects.create` and related row creation) to persist the order. It also uses a custom method (`add_hidden_arrival`) to link the order to a location, illustrating how business logic can be embedded in model methods rather than external visualization tools. The rendering approach is not visual; it is a server-side data-handling example.

Aandybak
69% match
Loading thumbnail…

Gist 9295126fbe6657c96185

This visualization shows the relationship between Django model fields and their cached property aliases in a database schema. It uses the Django ORM’s `models.DateTimeField` and `models.ForeignKey` to define the base order row’s timestamp and two related inventory item references, while `@cached_property` methods expose either the confirmed stock item or the unconfirmed item model. The code demonstrates how `is_confirmed` switches between the two foreign keys, returning `None` for the unused one. The example relies on Django’s model inheritance and the `cached_property` decorator to manage lazy-loaded relationships, illustrating a pattern where alternate field names are hidden behind a single logical accessor.

Aandybak
67% match
Loading thumbnail…

Django ORM subquery example

This example demonstrates how to translate a SQL query into Django’s ORM to filter consignments that are not linked to any booking with a “quote” status. It shows the equivalent raw SQL with nested subqueries and LEFT OUTER JOINs, alongside the Python code using `Consignment.objects.filter()` with `Q` objects and `.exclude()`. The code then prints the status of each resulting consignment’s content object. It relies on Django’s ORM methods `filter`, `exclude`, and `Q`, with the data sourced from logistics and office booking models.

Aandybak
66% match
Loading thumbnail…

Gist 9514739

This visualization displays hire volume as an aggregate sum of booking stock quantities over time, using a bar-chart template sized at 580x200 pixels. The chart draws from a Django queryset of BookingStockItem records, filtering by the estimated dispatch date field and aggregating quantities with Django’s `Sum` function. The data is rendered on a daily interval, and the chart class extends a custom `BaseChart` with a title and chart template. The implementation relies on Django’s ORM for data retrieval and aggregation, with the visualization output presumably using a charting library within the specified template, though the code snippet does not expose the exact front-end rendering library.

Aandybak
65% match
Loading thumbnail…

Gist c99a8e7213158cfd1ec8

The visualization tracks consignment movements by filtering query sets for departures from and arrivals at base locations, distinguishing deliveries, collections, and items in transit. It shows the flow of goods between origins and destinations, with transit defined as the union of completed deliveries and collections. The code relies on Django’s queryset API with `Q` objects for location-based filtering, using `exclude` to isolate timed events, and combines results via set union. No specific charting library appears; the rendering approach is not visible in this snippet, focusing instead on data preparation.

Aandybak
64% match