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
We've discussed this before but I didn't create an issue for it.
Currently APOC stores information on triggers, custom procs, uuid-handler, etc. in the system database.
As an configuration option it should be possible to also store this information in the current database, which would also alleviate some of the cluster leaderships issues, but with the drawback that there would be additional nodes that don't belong to the actual graph data in the current db.
This would also cover the issues that triggers or custom procedures are deleted when a database is deleted.
The text was updated successfully, but these errors were encountered:
We probably also need to provide some migration path, if apoc currently uses teh system db and the setting is changed, then it should move the information to the current db.
Need to look at what's happening with global settings that span multiple databases, perhaps write them to the neo4j database.
We've discussed this before but I didn't create an issue for it.
Currently APOC stores information on triggers, custom procs, uuid-handler, etc. in the system database.
As an configuration option it should be possible to also store this information in the current database, which would also alleviate some of the cluster leaderships issues, but with the drawback that there would be additional nodes that don't belong to the actual graph data in the current db.
This would also cover the issues that triggers or custom procedures are deleted when a database is deleted.
The text was updated successfully, but these errors were encountered: