Wichert Akkerman wrote: > Which outputs: > > 2010-01-15 12:30:00+01:00 > 2010-08-15 12:30:00+01:00 > > > The second timestamp should have +02:00 as timezone due do daylight > saving differences. Unfortuantely the timezone information reported on > the column has a fixed offset instead of the more informative > Europe/Amsterdam time. > > I am guessing that this is mostly due to psycopg2 not handling timezones > properly. I am wondering if SQLAlchemy itself will handle this correctly > if psycopg2 would do the right thing, and if other dialects implement > this better?
Its true, we don't do anything with the date objects passed to/from psycopg2, so you'd have to ask them about best practices for handling timezone-aware dates. Personally I don't use them, I try to store everything as UTC across the board and deal with timezone conversions only at the point of data collection and display. > > Wichert. > > -- > You received this message because you are subscribed to the Google Groups > "sqlalchemy" group. > To post to this group, send email to sqlalch...@googlegroups.com. > To unsubscribe from this group, send email to > sqlalchemy+unsubscr...@googlegroups.com. > For more options, visit this group at > http://groups.google.com/group/sqlalchemy?hl=en. > > -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To post to this group, send email to sqlalch...@googlegroups.com. To unsubscribe from this group, send email to sqlalchemy+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/sqlalchemy?hl=en.
