-
Notifications
You must be signed in to change notification settings - Fork 276
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
Minor release of v9 with seabolt support? #1599
Comments
Yes, this is probably possible with the right version of neo4j-ruby-driver. @jjg-dressipi could make a PR to the 9.6.x branch with all the changes needed to make it work of if only the changes above could you describe the tricks you had to apply? |
Many thanks, I'll make that PR shortly. May be best to describe the changes here. This is for a Rails 5 API-only application. First, you need to have some configuration options set in Modify
Modify
Modify
and so on. |
@jjg-dressipi neo4j-9.6.2 released! |
Great -- thanks! |
Just a note to confirm that this fixes the issue with my application: my Gemfile now reads
which should coerce and maintain the version restrictions mentioned above by @klobuczek |
I've been experimenting with the seabolt driver on my v9.6 application, it's a bit tricky to set-up, but once done it's fast and reliable -- everything works except one thing: attempting to load the schema results in a
Neo4j::Driver::Exceptions::ClientException
"Cannot perform data updates in a transaction that has performed schema updates.". Looking at the 9.6.1 source locally, modifyinglib/neo4j/tasks/migration.rake
fromto
Fixes the issue. I see you have already done the same in master.
So could I request that there is a minor release of the v9 branch (9.6.2?) which back-ports this two-line fix enabling use of Seabolt? I'll be jumping on v10 as soon as it's out of beta, but I'm sure there are those who will be using v9 for some time yet.
The text was updated successfully, but these errors were encountered: