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
I'm evaluating Shaolinq hoping to replace our npgsql-only implementation, to get real ORM and support for Linq, and so far I really like it!
I do have an issue when I insert new item with a timestamp (without timezone) column, the time ending up in the db is UTC (currently one hour off for me in Sweden). In the docs for npgsql (http://www.npgsql.org/doc/datetime.html) you can see that they don't touch the DateTime when the column is timestamp, but Shaolinq seems to always change it to UTC (see UniversalTimeNormalisingDateTimeSqlDateType.cs).
Is that really a correct behavior?
Thanks!
/Roger
The text was updated successfully, but these errors were encountered:
Hi,
I'm evaluating Shaolinq hoping to replace our npgsql-only implementation, to get real ORM and support for Linq, and so far I really like it!
I do have an issue when I insert new item with a timestamp (without timezone) column, the time ending up in the db is UTC (currently one hour off for me in Sweden). In the docs for npgsql (http://www.npgsql.org/doc/datetime.html) you can see that they don't touch the DateTime when the column is timestamp, but Shaolinq seems to always change it to UTC (see UniversalTimeNormalisingDateTimeSqlDateType.cs).
Is that really a correct behavior?
Thanks!
/Roger
The text was updated successfully, but these errors were encountered: