You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
I am currently building an API service to use ontop of our sqlserver instance. We have an existing database that is managed by a third party that has used the DATETIME data type to store dates for date_created, date_last_modified. All of these dates are stored in our local time zone "-5 GMT".
Describe the solution you'd like
Would it be possible to add a parameter in the dsn that specifies a global offset for all DATETIME data types?
Describe alternatives you've considered
Documentation on how the driver can be extended to support adding the Location value to the time.Time structure globally.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
I am currently building an API service to use ontop of our sqlserver instance. We have an existing database that is managed by a third party that has used the DATETIME data type to store dates for
date_created
,date_last_modified
. All of these dates are stored in our local time zone "-5 GMT".Describe the solution you'd like
Would it be possible to add a parameter in the dsn that specifies a global offset for all
DATETIME
data types?Describe alternatives you've considered
Documentation on how the driver can be extended to support adding the
Location
value to thetime.Time
structure globally.The text was updated successfully, but these errors were encountered: