Why Database Time Zone Handling Breaks Queries

Failed to add items

Sorry, we are unable to add the item because your shopping cart is already at capacity.

Add to basket failed.

Please try again later

Add to wishlist failed.

Please try again later

Remove from wishlist failed.

Please try again later

Adding to library failed

Please try again

Follow podcast failed

Unfollow podcast failed

Why Database Time Zone Handling Breaks Queries

Listen for free

View show details

In this episode of Database Tech with Fexingo, Lucas and Luna dive into the hidden chaos of time zone handling in databases. Using the real-world example of a popular booking platform that lost millions in revenue due to incorrect time zone conversions, they explore why most developers underestimate the complexity. They discuss the difference between TIMESTAMP WITH TIME ZONE and TIMESTAMP WITHOUT TIME ZONE in PostgreSQL, how indexing breaks when time zones shift, and why daylight saving time transitions cause silent data corruption. The episode also covers practical strategies like storing all timestamps in UTC at the database level, using application-layer time zone conversion, and the importance of testing edge cases like the 'spring forward' and 'fall back' moments. Listeners will learn one concrete lesson: always store timestamps in UTC and convert at query time—unless you want your midnight reports to include yesterday's data. #DatabaseTimeZones #SQLTimestamp #PostgreSQL #UTCDatabase #DaylightSavingTime #QueryPerformance #DataIntegrity #TimeZoneHandling #DatabaseDesign #TechPodcast #DatabaseTech #FexingoBusiness #BusinessPodcast #SoftwareEngineering #BackendDevelopment #DataEngineering #SQLTips #DatabaseOptimization Keep every episode free: buymeacoffee.com/fexingo

No reviews yet