Improve apoc.periodic.iterate docs

[neo-technology-build-agent]

Issue by conker84
Monday May 24, 2021 at 09:23 GMT
Originally opened as neo4j-contrib/neo4j-apoc-procedures#1914

---

there are many people who have issues with periodic iterate in 4.x when you return nodes and rels from the driving statement and then update them in the update statement.
Since 4.x that might cause the actual change data to be attached to the outer transaction.
So one solution here is to just return id(n) or id(r) from the first query and look them up again in the inner query (e.g. where id(n) = id)
Can we update the docs for that and possibly also add a WARN section that points that out?

[hvub]

I am not sure I understand the issue. Can you provide a specific example?

Is the issue still present in the current version of the docs, anyway? --> https://neo4j.com/docs/apoc/current/overview/apoc.periodic/apoc.periodic.iterate/

Also users should rather use CALL IN TRANSACTIONS https://neo4j.com/docs/cypher-manual/current/subqueries/subqueries-in-transactions/ rather than apoc.periodic.iterate.