Skip to content

Fix bugs in neo4j.time.DateTime handling #1100

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

Merged
merged 2 commits into from
Oct 4, 2024

Conversation

robsdedude
Copy link
Member

@robsdedude robsdedude commented Oct 2, 2024

  • Fix DateTime +/- Duration computation being wildly off by considering the days of the DateTime since UNIX epoch twice.
  • Fix Result.to_df not correctly converting DateTimes with tzinfo if parse_dates=True is passed in.
  • Fix DateTime.__ne__ (inequality operator) always falling back to object.__ne__ (comparison by id).

@robsdedude robsdedude force-pushed the fix-datetime-handling branch 3 times, most recently from 1db9898 to 0ea8313 Compare October 2, 2024 09:17
 * Fix `DateTime` +/- `Duration` computation being wildly off by considering
   the days of the `DateTime` since UNIX epoch twice.
 * Fix `Result.to_df` not correctly converting `DateTime`s with `tzinfo` if
   `parse_dates=True` is passed in.
 * Fix `DateTime.__ne__` (inequality operator) always falling back to
   `object.__ne__` (comparison by `id`).
Copy link
Contributor

@MaxAake MaxAake left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@robsdedude robsdedude enabled auto-merge (squash) October 4, 2024 10:59
@robsdedude robsdedude merged commit 12f50b9 into neo4j:5.0 Oct 4, 2024
20 checks passed
@robsdedude robsdedude deleted the fix-datetime-handling branch October 4, 2024 14:43
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.

2 participants