Thank you Jeremy :) If I understand correctly, using Sequel's SQLite adapter with database_timezone set to :utc won't correctly in some cases like Tiago's example, correct? And I'm guessing that the new configuration variable could automatically match Sequel's database_timezone (or `Database#timezone`) if it wasn't for maintaining backwards compatibility?
It's a bit unfortunate that SQLite doesn't return a time zone in CURRENT_TIMESTAMP. In any case, I will then update the activerecord_connection extension to turn on the new configuration option for SQLite adapter when ActiveRecord's timezone is set to :utc (the default). Kind regards, Janko On Tuesday, May 19, 2020 at 5:59:01 PM UTC+2, Jeremy Evans wrote: > > On Tuesday, May 19, 2020 at 5:11:07 AM UTC-7, Tiago Cardoso wrote: >> >> Discussion opened here, with a few suggestions: >> https://github.com/janko/sequel-activerecord_connection/issues/1 >> >> Let me know what you think is the best solution. >> > > I've added support for keeping CURRENT_* in UTC to Sequel's SQLite > support: > https://github.com/jeremyevans/sequel/commit/5d056c3c8388a250bfffc5238a143d3fd745ce8d > > Thanks, > Jeremy > -- You received this message because you are subscribed to the Google Groups "sequel-talk" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sequel-talk/fa196556-6025-45a6-927c-6f46df3c034e%40googlegroups.com.
