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 believe the recent pull request #2386 tried to fix the behavior of timestamp columns (KotlinInstantColumnType, JavaInstantColumnType) to always store values in UTC.
However, on my system with SQLite, retrieving timestamps from a database results in the UTC timestamps being interpreted as if they were in my system local time zone.
I believe the cause to be the following lines of code:
This uses ResultSet#getTimestamp(index), which yields timestamp objects which are in the system local time zone if no calendar object is explicitly passed.
The text was updated successfully, but these errors were encountered:
I believe the recent pull request #2386 tried to fix the behavior of timestamp columns (
KotlinInstantColumnType
,JavaInstantColumnType
) to always store values in UTC.However, on my system with SQLite, retrieving timestamps from a database results in the UTC timestamps being interpreted as if they were in my system local time zone.
I believe the cause to be the following lines of code:
Exposed/exposed-kotlin-datetime/src/main/kotlin/org/jetbrains/exposed/sql/kotlin/datetime/KotlinDateColumnType.kt
Lines 393 to 395 in a17743d
Exposed/exposed-java-time/src/main/kotlin/org/jetbrains/exposed/sql/javatime/JavaDateColumnType.kt
Lines 377 to 379 in a17743d
This uses
ResultSet#getTimestamp(index)
, which yields timestamp objects which are in the system local time zone if no calendar object is explicitly passed.The text was updated successfully, but these errors were encountered: