Closing Sales Across Time Zones is a practical PostgreSQL project for turning venue-local calendar dates into correct ticket-sales reports. Keep every original receipt, including separate tickets showing the same clock time, and deliver real CSV files.
One Guided Lab has three steps: derive local-day windows, build a complete ticket ledger, and export reports that keep their meaning across connection time zones. One independent Challenge applies the methods to London and Sydney. Each unit starts with its own synthetic data.
What You Will Learn
- Distinguish calendar dates, local clock readings, actual instants and named IANA zones.
- Convert both local midnights independently and use an inclusive opening with an exclusive closing.
- Preserve free tickets, repeated-clock receipts and venues with no sales.
- Save reusable SQL, produce explicit UTC output and read complete real CSV reports without source-data fallback.
Who This Course Is For
For beginners familiar with terminal navigation, PostgreSQL connections and SELECT/WHERE. Date/time conversions, query templates, joins and CSV syntax are explained before use. No Python or frontend development is required.
LabEx provides PostgreSQL, prepared ticket facts and the real reporting desk in browser-based Terminal. No local setup is needed.
Frequently Asked Questions
Does this cover real payment settlement?
It is a simplified historical ticket-sales closing with integer cents. Taxes, refunds, payment-provider settlement and accounting guarantees are outside the project.
Will the tool fix an incorrect query or ambiguous time?
No. It executes your saved SQL and exports actual rows; the file reader uses only saved CSV bytes. Inputs already identify instants with UTC or explicit offsets. Parsing ambiguous offsetless clock readings is outside the project. The Challenge uses methods fully practiced in the Guided Lab.
