Skip to content
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

Defer unknown zone information failures to datetime value access stage #1273

Merged
merged 2 commits into from
Jul 21, 2022

Conversation

injectives
Copy link
Contributor

@injectives injectives commented Jul 20, 2022

If server supplies zone information that is not supported by driver runtime, it will be represented by an unknown datetime value that fails on datetime access. This prevents an immediate failure during data consumption and allows usage of other values.

@injectives injectives force-pushed the feature/datetime branch 8 times, most recently from 56c05a1 to 1c9a11b Compare July 20, 2022 22:22
If server supplies zone information that is not supported by driver runtime, it will be represented by an unknown datetime value that fails on datetime access. This prevents an immediate failure during data consumption and allows usage of other values.
Copy link
Contributor

@bigmontz bigmontz left a comment

Choose a reason for hiding this comment

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

🕙 🕦

@injectives injectives merged commit 4179983 into neo4j:5.0 Jul 21, 2022
@injectives injectives deleted the feature/datetime branch July 21, 2022 13:08
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