Closed steenstral closed 1 year ago
I met the same issue, does anybody have a solution?
Hi all, we're working on this :) It comes from the fact that the we've used the local date time with your system time zone when sending data to TypeDB. It shouldn't be too hard to resolve but we want to make sure to be systematic about it. We're hoping to have this fixed and released early next week
@hezhichenghzc @steenstral FYI the release is out on github & pip, please let us know if there are any remaining issues :)
@flyingsilverfin Unfortunately I cannot test it yet, because there is a version mismatch between te client (2.18.1
) and the server (2.17.0
). When trying to create a client I get the following error:
```bash
Traceback (most recent call last):
File "c:\
I saw this issue also passing by on Discord. Is there a way I can test this patch update, or do I need to wait for the new TypeDB server release?
@steenstral
Unfortunately I cannot test it yet, because there is a version mismatch between te client (
2.18.1
) and the server (2.17.0
).
TypeDB 2.19 is available on the Releases page (https://github.com/vaticle/typedb/releases/tag/2.19.0), and in package managers like apt and brew.
I updated my TypeDB server version, and I can confirm that it is working and that I now get the expected result. Thank you for solving this issue!
Description
The Python client API is inconsistent with time zones. When a
datetime
attribute is inserted, everything is fine. However, when this same attribute is queried, there is an offset of 2 hours (UTC+01:00 + summertime).Environment
venv
with onlytypedb-client
installedReproducible Steps
KEYSPACE = "datetime_issue"
def main() -> None:
Create a client
if name == "main": main()
Actual Output
Instead, there is a clear offset in time, 1 hour in wintertime and 2 hours in summertime (exactly UTC+01:00).
Additional information
match
query in thedatetime_issue
keyspace inside of TypeDB Studio 2.11.0 on Windows, does NOT have this time offset. This means that the problem is clearly in the Python API, especially in thetransaction.query().match(query)
method.