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
Is your feature request related to a problem? Please describe.
The CQL date types as currently defined diverge from the (latest?) specification of CQL:
There is no timezone on Date and Time
Times use millis, not fractions.
Currently, we allow timezones on Date and Time and we use fractions internally (since DateTimeOffset uses fractions).
Describe the solution you'd like
We should strictly align with the spec and refuse to handle timezones and precisions beyond milliseconds.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The CQL date types as currently defined diverge from the (latest?) specification of CQL:
Currently, we allow timezones on Date and Time and we use fractions internally (since DateTimeOffset uses fractions).
Describe the solution you'd like
We should strictly align with the spec and refuse to handle timezones and precisions beyond milliseconds.
The text was updated successfully, but these errors were encountered: