PostgreSQL report generator reference — 2026-10-14
Synthetic order-fulfillment example, not customer data or AI-generated output.
Run reference.sql in a fresh disposable PostgreSQL connection. It creates only temporary objects.
Expected order: 000101 (6 days, 5 units), 000103 (4 days, 1 unit), 000105 (1 day, 4 units).
Expected data rows: 3; units: 10; maximum days overdue: 6.
As of 2026-10-14 00:00 at the agreed business-date boundary; no timezone conversion is modeled.
Status is assumed stable for this fixture. Real historical reporting needs status history/snapshots.
The SQL was checked locally in PGlite; this is not an AI accuracy or hosted product export test.
In the SAME psql session, a client-side export command is:
\copy (SELECT * FROM overdue_report ORDER BY days_overdue DESC, order_id) TO 'overdue-orders-2026-10-14.csv' WITH (FORMAT csv, HEADER true, ENCODING 'UTF8', NULL '\N')
The psql command is documented guidance, not an executed command in the local PGlite check.
Confirm overwrite behavior and output location before running it. Preserve order_id as text when importing.
CSV quoting preserves syntax, but does not neutralize spreadsheet formulas in untrusted text.
Temporary views do not carry over to an AYD connection. Have an owner provide an approved test view.