You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
EdgeDB currently lacks a native type for representing time-of-day with timezone information, which is crucial for applications that need to schedule recurring daily events across different time zones. While datetime handles timezone-aware timestamps well, it includes date information which is unnecessary for daily recurring events. The existing cal::local_time lacks timezone context.
Use Case Example
Sending daily reports to users in different time zones at their local 9 AM
Scheduling daily system maintenance during off-peak hours for different regions
Setting business hours for global operations
Configuring notification preferences for users across time zones
Current Workarounds
Using datetime requires storing redundant date information
Problem Statement
EdgeDB currently lacks a native type for representing time-of-day with timezone information, which is crucial for applications that need to schedule recurring daily events across different time zones. While
datetime
handles timezone-aware timestamps well, it includes date information which is unnecessary for daily recurring events. The existingcal::local_time
lacks timezone context.Use Case Example
Current Workarounds
datetime
requires storing redundant date informationcal::local_time
loses timezone contextcal::local_time
and timezone strings require manual timezone handlingProposed Solution
Add a new
cal::zoned_time
type that:The text was updated successfully, but these errors were encountered: