-
Notifications
You must be signed in to change notification settings - Fork 157
feat(unsupportedType): add support for Bolt Unsupported Type #1691
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
Conversation
4d1163e
to
c5ac185
Compare
ed518bb
to
0eacbc7
Compare
4051187
to
ce5a9bb
Compare
So we are not giving the user access to the raw binary data it seems? Fine with me, thought it would be different though |
ce5a9bb
to
1c5ad27
Compare
No, unfortunately this would not be available on Bolt level. The reasons are in ADR-033 that is still open. |
This update adds support for a new `TypeSystem#UNSUPPORTED()` type. The unsupported type may occur when a new type is introduced in the Neo4j server and the driver is connected over an older Bolt Protocol version that does not support this type. A new `UnsupportedTypeData` object provides information about the unsupported type and the minimum Bolt version needed to support it. However, the `UnsupportedTypeData` object itself requires at least Bolt Protocol 6.0.
1c5ad27
to
2922b94
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✅
This update adds support for a new
TypeSystem#UNSUPPORTED()
type. The unsupported type may occur when a new type is introduced in the Neo4j server and the driver is connected over an older Bolt Protocol version that does not support this type. A newUnsupportedType
object provides information about the unsupported type and the minimum Bolt version needed to support it. However, theUnsupportedType
object itself requires at least Bolt Protocol 6.0.