Ticket #54 (assigned enhancement)

Opened 5 years ago

Last modified 4 years ago

Support multiple time zones for temporal data

Reported by: psmeros Owned by: mple
Priority: major Milestone: Strabon v3.2.11
Component: runtime Version:
Keywords: Cc:


Since Strabon now supports temporal functions, we have to decide what we will do with the time zones.

One solution is to follow the "SRID" approach that we used for the geometries: Store time zone in the database, and convert each time we apply a temporal function.

A lazier solution is to convert to UTC when we store our data and then apply any temporal function we want without a problem. It is obvious that with this approach we lose the original time zone. But do we need it?

More details for the datetime format here: http://www.w3.org/TR/NOTE-datetime.

Change History

comment:1 Changed 5 years ago by charnik

I think yes, you need to store it, because when the user projects on such a value, she would like to get what she inserted.

comment:2 Changed 4 years ago by psmeros

  • Milestone set to Strabon v3.2.10

comment:3 Changed 4 years ago by psmeros

  • Owner changed from pyravlos-team to mple
  • Status changed from new to assigned
Note: See TracTickets for help on using tickets.