It depends on your usecase, most end-users are fine with inconsistencies (as
they are part of real life).
- first approach adds too much overhead
- second approach will also run into inconsistencies as neo4j's transaction
isolation is "read-comitted"
so it would be most sensible to cater for the inconsistencies in your API.
Michael
Am 29.11.2011 um 18:58 schrieb D. Frej:
> Hi,
>
> I have an architectural question regarding an applicaiton using neo4j.
> This is the situation: it is a application with the functionality to
> show big data in list form. However, when delivering the data in two
> steps and records are deleted meanwhile the list might be incosistent...
> What is the best way (best practise?) to do this?
>
> - putting all records in a collection and return them all at once?
> - keep the transaction open and assigened to the session?
> - deliver the data in several steps and risk inconsistency?
>
> Any experience? Any suggestions?
>
> Didi
> ___
> Neo4j mailing list
> User@lists.neo4j.org
> https://lists.neo4j.org/mailman/listinfo/user
___
Neo4j mailing list
User@lists.neo4j.org
https://lists.neo4j.org/mailman/listinfo/user
