Skip to content

v0.3.3 - Timezone-Aware DateTime Fix

Choose a tag to compare

@doganarif doganarif released this 11 Nov 01:45
· 5 commits to main since this release
0655c53

馃悰 Bug Fix

Timezone-Aware DateTime Support (Fixes #34)

Fixed incorrect timestamp display across different timezones by ensuring all DateTime columns use timezone-aware storage.

馃敡 What Changed

  • Database Storage: All SQLAlchemy DateTime columns now use DateTime(timezone=True)
  • PostgreSQL: Uses TIMESTAMPTZ (timestamp with timezone) for proper timezone handling
  • SQLite/DuckDB: Stores ISO format strings with timezone information
  • UTC Timestamps: All datetime values continue to use datetime.now(timezone.utc) for consistent UTC storage

馃幆 Impact

Before this fix, timestamps were stored as naive datetimes in the database, causing the dashboard to display incorrect times for users in different timezones. Now, all timestamps are properly stored with timezone information and displayed correctly regardless of the user's timezone.

鈿狅笍 Database Compatibility

This change is backward compatible. The update affects how data is stored in the database, not the API. Existing data will continue to work, and new entries will benefit from timezone-aware storage.

馃摝 Installation

pip install --upgrade fastapi-radar==0.3.3

馃檹 Thanks

Thanks to @vk496 for reporting this issue!

Full Changelog: v0.3.2...v0.3.3