We are importing data from one DB to another. The source DB (MySQL) has several tables that store timestamps in UTC in datetime columns. The destination DB (SQL Server) needs to store timestamps in the local timezone. Sequel.application_timezone and Sequel.database_timezone are global so the timestamp is converted to local on read and back to utc on write. Is there a way to accomplish this without having to modify the code that does the import to identify/convert datetime columns before they are written?
We realize that UTC is the right way to store timestamps but unfortunately the application interacts with several other databases that do not use UTC. Thanks, Rohit -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/sequel-talk?hl=en.
