Re: [Neo4j] Database constraints have changed error what is the actual behavior

2018-04-23 Thread 'Mattias Finné' via Neo4j
The exception is that the database schema changed from the point your "other" schema-changing transaction up to the time it wanted to commit. The exception has a transient status code, which at least from the embedded API results in a org.neo4j.graphdb. TransientFailureException which means tha

Re: [Neo4j] Database constraints have changed error what is the actual behavior

2018-04-23 Thread George & Sherin
Since I was using some code to generate dynamic indexes I could not extract the problematic piece easily from the unmanaged extension we have. I tried to create a simple utility which tries to do the same as the other code with and embedded db But the problem is that it times out on index creation

Re: [Neo4j] Database constraints have changed error what is the actual behavior

2018-04-14 Thread George & Sherin
Sure will do that later today or tommorow On Sat, Apr 14, 2018 at 5:52 PM, 'Michael Hunger' via Neo4j < neo4j@googlegroups.com> wrote: > Would you mind creating a GitHub issue at github.com/neo4j/neo4j sharing > your commands and error message > > You didn't share the actual queries that create

Re: [Neo4j] Database constraints have changed error what is the actual behavior

2018-04-14 Thread 'Michael Hunger' via Neo4j
Would you mind creating a GitHub issue at github.com/neo4j/neo4j sharing your commands and error message You didn't share the actual queries that create the ` :12356Person`. Michael On Fri, Apr 13, 2018 at 5:38 AM, George & Sherin wrote: > Already present Constraint create constraint on (n:Ten

Re: [Neo4j] Database constraints have changed error what is the actual behavior

2018-04-13 Thread Kamal Murthy
Hi George, Here is my suggestion: Create nodes: Tenant and Tenants (your tenantidPersons) 1. create constraint on (n:Tenant) assert n.id is unique 2. create constraint on (p:Tenants) assert p.ssn is unique Data model:

Re: [Neo4j] Database constraints have changed error what is the actual behavior

2018-04-12 Thread George & Sherin
Already present Constraint create constraint on (n:Tenant) assert n.id is unique each of this transaction contain Txn1 create (n:Tenant {id:1234}) create constraint on (n:1234Person) assert n. ssn is unique Txn2 create (n:Tenant {id:12356}) create constraint on (n:12356Person) assert