Greetings! Am working on spinning your example up (very cool btw) - gettting an error

[mimomenome]

Neo4j.Driver.ClientException: 'Cannot perform data updates in a transaction that has performed schema updates.'

This exception was originally thrown at this call stack:
Neo4j.Driver.Internal.MessageHandling.ResponsePipelineError.EnsureThrownIf(System.Func<System.Exception, bool>)
Neo4j.Driver.Internal.Result.ResultCursorBuilder.ConsumeAsync()
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
Neo4j.Driver.Internal.AsyncTransaction.DiscardUnconsumed()
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
Neo4j.Driver.Internal.AsyncTransaction.CommitAsync()
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
Neo4j.Driver.Internal.AsyncTransaction.CommitAsync()
System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
...
[Call Stack Truncated]

any ideas?

[willhl]

Ah yes I know why this is happening, it's caused by the schema change the Neo4j client does to ensure the IDs are unique (CREATE CONSTRAINT ON(nc:{0}) ASSERT nc.Id IS UNIQUE).

I actually thought this was fixed because I separated out the schema changes from everything else... I'l have a check to see what's going on, might be that the git submodule isn't pulling in the correct version.

[edit]
I'm also not sure the schema change is necessary or appropriate where it is, needs a rethink.

[mimomenome]

I'll check to see that I have the latest version - I was able to get it working by removing the constraint, but of course that is not ideal likely..Its the constraint being applied in the same transactional boundary as the commits. The way we have been addressing this with a similar case is generating the schema first, but this requires iterating the collection to identify labels prior to running the data commits..