Introduce driver level Hydration and Dehydration hooks - #1157
Draft
bigmontz wants to merge 2 commits into
Draft
Conversation
This hooks enable driver users to globaly map their own data types to Neo4j driver types and vice-versa.
bigmontz
force-pushed
the
5.x-hydration-hooks
branch
from
November 2, 2023 12:50
a889c03 to
e191168
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This hooks enable driver users to globaly map their own data types to Neo4j driver types and vice-versa.
Example:
The driver is able to hydrate
Duration,LocalTime,LocalDateTime,Time,Date,DateTimeandPoint. Other types will not able to be hydrated since they are used by driver internals and the hydration step occurs while data is being received from the socket.Dehydration, in other hand, can be done from any data type since it got converted to types which driver can understand.