It's not only an issue with TransactionDataImpl. All the internal state in
a transaction is kept without ordering information because neo4j doesn't do
ordering guarantees in general. It would require a bigger change and could
introduce memory and performance overhead to do so. Why is the order
Hi,
We use the Neo4JCommitListener to synchronize some neo4j data back to a
database.
I have an issue when trying to deal with the delete events.
I delete nodes in a particular order in neo4j (it's a nested set, so down-up
), but when getting the events in the commitListener the order is not
2 matches
Mail list logo
