You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 1, 2021. It is now read-only.
The driver seems to handle bolt protocol v1 only. I try to update/return object types as parameters (ex : Point) and the server returns this message "Point is not supported as a return type in Bolt protocol version 1. Please make sure driver supports at least protocol version 2. Driver upgrade is most likely required."
As I do not see any new commit for 2 years, I wonder if the driver is still maintained, but I absolutely need to find a solution to manage those types because some of my queries are based on distance calculations and I have a index on a point property. Also, I would like to keep the benefits of parameters and avoid harcoding the point directly in the query.
Does anyone know if I can use any workaround of if an update is sheduled for the driver ?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The driver seems to handle bolt protocol v1 only. I try to update/return object types as parameters (ex : Point) and the server returns this message "Point is not supported as a return type in Bolt protocol version 1. Please make sure driver supports at least protocol version 2. Driver upgrade is most likely required."
As I do not see any new commit for 2 years, I wonder if the driver is still maintained, but I absolutely need to find a solution to manage those types because some of my queries are based on distance calculations and I have a index on a point property. Also, I would like to keep the benefits of parameters and avoid harcoding the point directly in the query.
Does anyone know if I can use any workaround of if an update is sheduled for the driver ?
The text was updated successfully, but these errors were encountered: