Single query limitations

I am wondering if there is any limitation I should be aware of when creating parameters and using a transaction with several merge statements?

From the image the node selected inclusive and to the left, for this statement I can create up to 75 different directly connected nodes - the light purple, each with 1 to N elements.

But I have another denser example that will have a significantly large number of params and nodes to create, which will also need a transaction to be created.

Thanks!

Are you using individual nodes to store each parameter?

No specific limitations that I can think of.

@glilienfield @joshcornejo

just dont try to commit 100k++ changes in a single txn otherwise you may encounter a out of heap error

2 Likes

I have several properties per node (somewhere between 3 and 12), but the edges from the little purple go 1 to the yellow nodes, but 1:N to any other, and for those the query checks if it has to create a node, update a node, or update an edge.

So creating 7 nodes and a few edges turned to 300 lines of params and cypher.

Thanks - great to know, I doubt it will be that big per transaction, i would think that it can reach an average of around 1K - 2K for the more complex graph.