Skip to main content
100%

Gist 8865235

✓ Published0🌍 Public
Aandybak
Last edited Feb 7, 2014
Created on Feb 7, 2014

A Django model method updates inventory records by deleting any stock counts with a timestamp at or after a given time, then inserting a new count for that item. The `set_stock_count` function filters `StockCount.objects` using `timestamp__gte`, removes matching entries, and creates a fresh record with the supplied stock level. This demonstrates a time-series upsert pattern for tracking product availability over time, though the code shows no visualization logic, only the data-management layer.

AI-generated description

Similar vizzes

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
65% match
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
65% match
Loading thumbnail…

Gist 11250891

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.

Aandybak
63% 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
62% 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
61% 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
60% match
Loading thumbnail…

Gist fd2387f597641c4a52a7

This visualization displays the movement of consignments over time, plotting each item’s journey from start to end location based on timestamps. The code queries logistics data with Django ORM, filtering out consignments linked to bookings with a specific status, then renders the results as a temporal flow. It uses D3.js’s `d3.forceSimulation` to position nodes representing locations and consignments, while `transition.attrTween` animates the paths between them. The rendering approach relies on SVG elements, with the data sourced from a PostgreSQL database via the raw SQL query shown.

Aandybak
55% match
Loading thumbnail…

Gist 9839271

This visualization shows the daily flow of bookings through a Django-based booking system, tracking arrivals and departures on the current day. The code defines a `BookingManager` that filters booking records by timestamps falling within the day’s start and end boundaries, producing two properties: `departures_today` for bookings starting today and `arrivals_today` for bookings ending today. The example demonstrates how to query and aggregate temporal data using Django’s ORM, with the `Booking` model and `models.Manager` class providing the data structure. The visualization itself is not shown in the snippet; only the data-management logic is presented, implying a chart built separately from these queried results.

Aandybak
54% match