On Monday, July 16, 2018 at 11:30:47 PM UTC-7, [email protected] 
wrote:
>
>
> Hi Folks,
>
> What's the current status of functionality and planned work for timestamps 
> with timezone offsets, especially MS SQL Server's datetimeoffset data type?
>
> I need to modify an app to support the storage of datetimes with varying, 
> world-wide offsets. Currently the support is weak but I'm willing to put in 
> the work to get it happening. Ideally, any code I write will give a decent 
> framework for accommodating other db engines in the future when other 
> interested parties put in the effort for their favourite/mandated engines...
>
> So far I've been dabbling with little hacks in my installed Sequel gem, 
> but I'm feeling ready to make a fork and get started properly. I'd 
> appreciate it if someone (Jeremy in particular?) can offer a bit of 
> guidance to make sure it's going to be flexible enough to accommodate other 
> engines, other development styles, and also safe for existing users of 
> Sequel regardless of their backend db engine.
>
> I have a formal plan in mind for my app, regarding appropriate choice of 
> data types both in the MS database and within the Ruby code. It would 
> probably bore less people to share that plan directly with whoever offers 
> guidance. My plan would impose rules that should probably be enabled using 
> a plugin, settings or extension, since I believe they could be breaking 
> changes for some projects that are currently playing loose with Ruby's Time 
> and DateTime datatypes (i.e. just like the project I'm working on)
>

Sequel doesn't really handle timezones by default, but it does ship with 
fairly comprehensive support for handling them.  
See http://sequel.jeremyevans.net/rdoc/classes/Sequel/Timezones.html.  So I 
don't think you need to write a framework to handle timezones, such a 
framework already exists and works well on most databases supported by 
Sequel.

I'm not sure how good the support is for the MSSQL datetimeoffset type.  
Sequel doesn't use that type by default (it uses datetime for 
Time/DateTime).  If there are datetimeoffset specific features that need to 
be added to Sequel, I'm open to that as long as they are backwards 
compatible by default.

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 post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/sequel-talk.
For more options, visit https://groups.google.com/d/optout.

Reply via email to