-
Notifications
You must be signed in to change notification settings - Fork 198
MATCH with neotime.Datetime params on value datetime("2019-10-30T07:54:02.129790999[UTC]") #306
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
Labels
Comments
Same problem with datetime value = "2019-10-31T05:41:16.065365999[UTC]" |
Looks like a possible rounding/precision issue, likely around passing
|
This have been fixed with PR #412 for the upcoming 4.0.0 driver. |
For driver 1.7 that uses |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Example bug report
Can not MATCH with datetime value: "2019-10-30T07:54:02.129790999[UTC]
Neo4j Version: : 3.5.11 Community
Neo4j Mode: Single instance
Driver version: Python driver 1.7.5
(Python lib: neo4j==1.7.5, neobolt==1.7.15, neotime==1.7.4)
Operating System: Window 10 64bit
Steps to reproduce
Start Neo4j.
Run a query with browser:
CREATE (t:TEST {update_date:datetime("2019-10-30T07:54:02.129790999[UTC]")})
Run python code
Expected behavior
Out put is:
<Node id=248 labels={'TEST'} properties={'update_date': neotime.DateTime(2019, 10, 30, 7, 54, 2.129790999, tzinfo=)}>
Have record
<Node id=248 labels={'TEST'} properties={'update_date': neotime.DateTime(2019, 10, 30, 7, 54, 2.129790888, tzinfo=)}>
Actual behavior
Out put is:
<Node id=248 labels={'TEST'} properties={'update_date': neotime.DateTime(2019, 10, 30, 7, 54, 2.129790999, tzinfo=)}>
The text was updated successfully, but these errors were encountered: