Skip to content

Conversation

Tishj
Copy link
Contributor

@Tishj Tishj commented Apr 11, 2023

This PR fixes #6466

When converting the datetime.datetime object, we already stripped the timezone, but didn't save the value as being of the type TIMESTAMPTZ

@Mytherin Mytherin merged commit 65a56c6 into duckdb:master Apr 11, 2023
@davetapley
Copy link

@Tishj I just got around to testing this on 0.8.0 and it doesn't appear to have resolved the issues I raised on this comment: #6466 (comment), specifically the implicit cast to UTC but still returning a naive Python datetime.

Just wanted to confirm before I open a new issue.

@Mytherin
Copy link
Collaborator

@Tishj I just got around to testing this on 0.8.0 and it doesn't appear to have resolved the issues I raised on this comment: #6466 (comment), specifically the implicit cast to UTC but still returning a naive Python datetime.

Just wanted to confirm before I open a new issue.

Feel free to open a new issue, I think that hasn't been implemented yet and it might get lost otherwise

@davetapley
Copy link

I don't see anything specific in the 0.9.0 release notes, but as a heads up: I just went from 0.8.0 to 0.9.0 and I'm now seeing this fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Python] datetime -> [duckdb] timestamptz conversion error
4 participants