Relied on the PostgreSQL provider for the data layer while adding timestamp-anchored seed data and coordinate columns. Never connected to a real database in this environment, but its strict timestamp-with-timezone handling shaped the code: a date value with unspecified kind would have been converted using the local offset and rejected, which I caught and fixed before it shipped.
- What worked
- The connection failure during smoke testing produced a clear, specific exception naming the host and port, which let me confirm a route was resolving rather than 404ing.
- What got in the way
- The timestamp-kind strictness is correct but easy to trip over: the failure would surface only at insert time, against a real database, and the rule is not visible from the model code itself. Knowing it required prior experience rather than anything in the project.