Working with Dates and Times¶

Write Path¶

When inserting timestamps, the driver handles serialization for the write path as follows:

If the input is a datetime.datetime, the serialization is normalized by starting with the utctimetuple() of the value.

• If the datetime object is timezone-aware, the timestamp is shifted, and represents the UTC timestamp equivalent.

• If the datetime object is timezone-naive, this results in no shift – any datetime with no timezone information is assumed to be UTC

Note the second point above applies even to “local” times created using now():

>>> d = datetime.now()

>>> print(d.tzinfo)
None

These do not contain timezone information intrinsically, so they will be assumed to be UTC and not shifted. When generating timestamps in the application, it is clearer to use datetime.utcnow() to be explicit about it.

If the input for a timestamp is numeric, it is assumed to be a epoch-relative millisecond timestamp, as specified in the CQL spec – no scaling or conversion is done.

Read Path¶

The driver always assumes persisted timestamps are UTC and makes no attempt to localize them. Returned values are timezone-naive datetime.datetime. We follow this approach because the datetime API has deficiencies around daylight saving time, and the defacto package for handling this is a third-party package (we try to minimize external dependencies and not make decisions for the integrator).

The decision for how to handle timezones is left to the application. For the most part it is straightforward to apply localization to the datetimes returned by queries. One prevalent method is to use pytz for localization:

import pytz
user_tz = pytz.timezone('US/Central')
timestamp_naive = row.ts
timestamp_utc = pytz.utc.localize(timestamp_naive)
timestamp_presented = timestamp_utc.astimezone(user_tz)

This is the most robust approach (likely refactored into a function). If it is deemed too cumbersome to apply for all call sites in the application, it is possible to patch the driver with custom deserialization for this type. However, doing this depends depends some on internal APIs and what extensions are present, so we will only mention the possibility, and not spell it out here.

Write Path¶

For simple (not prepared) statements, the input values for each of these can be either a string literal or an encoded integer. See Working with dates or Working with time for details on the encoding or string formats.

For prepared statements, the driver accepts anything that can be used to construct the util.Date or util.Time classes. See the linked API docs for details.

Read Path¶

The driver always returns custom types for date and time.

The driver returns util.Date for date in order to accommodate the wider range of values without overflow. For applications working within the supported range of [datetime.MINYEAR, datetime.MAXYEAR], these are easily converted to standard datetime.date insances using Date.date().

The driver returns util.Time for time in order to retain nanosecond precision stored in the database. For applications not concerned with this level of precision, these are easily converted to standard datetime.time insances using Time.time().