Sequel currently uses timezones in timestamps on SQLite, which breaks SQLite's datetime functions (http://sqlite.org/lang_datefunc.html). I'm considering making that optional and having it off by default. That would increase compatibility with other SQLite code, but could break backwards compatibility with databases created with previous versions of Sequel depending on how they used the support.
Does anyone currently use Sequel's timezone support in timestamps on SQLite? Would anyone object to me breaking backwards compatibility (with a single method call to restore previous behavior)? The reason I'm asking this question now is I'm adding support to emulate the SQL extract method on SQLite, and it requires using SQLite's datetime functions. The choice is either to break backwards compatibility by default, or to break extract emulation and SQLite datetime function use in general by default. Jeremy -- 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.
