-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't discard the timezone information when reading timezone with tim… #196
base: main
Are you sure you want to change the base?
Conversation
Which DB are you using? |
I tested this using duckdb
…On Sat, 6 Apr 2024 at 07:11, Jules Ivanic ***@***.***> wrote:
Which DB are you using?
—
Reply to this email directly, view it on GitHub
<#196 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAO73SVWOSS2YG7YNP2E4HDY357ZDAVCNFSM6AAAAABFZIRB3OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANBQHE3DSNRRGA>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Is there anything else you need to get more confidence on this change? |
@olivierdeckers Can you please add some tests? |
} yield zConnection | ||
) | ||
|
||
case class OffsetDateTimeRow(value: OffsetDateTime) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When using query[OffsetDateTime] directly things were working already, the code path I changed in JdbcDecoder is only hit when using the JdbcDecoder.fromSchema
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Without the change, the case class would have had to have an Instant field instead of an OffsetDateTime field.
The data would be returned in the default system timezone, but interpreted as a timestamp in UTC. Where I live this results in a 2 hour offset currently between writing and reading an OffsetDateTimeRow
…estamp from the database