-
Notifications
You must be signed in to change notification settings - Fork 71
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
Problem writing to 4.1x #137
Comments
It looks like you're trying to write to the database within a read session. Can I see your code? |
The same code though works on 4.0x.
and the driver error on the catch
Is there some sort of config that tells the driver to go into write mode on 4.1x? If so, is it set on the env? I couldn't find anything on the documentation. This code worked for some time now, it's just that we decided to upgrade the actual DB to 4.1 |
|
This throws a different error, |
This will depend on the data held in From the docs:
https://neo4j.com/docs/cypher-manual/current/syntax/values/#property-types If you update the properties through the OGM it'll take care of the conversion for you. Can you create a repository that replicates the issue? That way I can advise how to fix the problem or if there is a bug in neo4j or the driver itself I can pass it on to the correct people to get it fixed. |
After some digging around it looks that it's a driver issue. Same code and payload react differently the moment you change the DB version. So for now it seems upgrading is a no go cause of the extend of the rewrites required |
Can you link me to a repo that replicate the issue? If it's a driver/database issue then I can pass it on to the right people to make sure it's safe for you to upgrade and stop others from running into the same problem. |
Upgraded to 4.1x (tried most of the minor updated all the way to 4.1.1) causes the following error any time a write is attempted
Neo4jError: Writing in read access mode not allowed. Attempted write to internal graph 0
Using the Neo4J browser works just fine. Downgrading to 4.0.x also works just fine.
Anyone else had this?
The text was updated successfully, but these errors were encountered: