2010/1/12 Laurent Laborde <[email protected]>: > On Tue, Jan 12, 2010 at 7:46 PM, Ryan Levering <[email protected]> wrote: >> Then this wouldn't be M-V-C, it would be M/C-V. The point of having >> that separate layer is that you don't need to worry about the model >> abstraction. Generally, controller level transactions should only >> exist because you actually want to force multi-operation atomicity, >> not because you know the underlying database needs to be >> transactionalized. And again, if your controller is doing a lot of >> reading, it will have to be split up into multiple transaction blocks. > > But, how do you split a "Traverse the complete graph" ? http://wiki.neo4j.org/content/Transactions#Big_transactions touched that subject... it could be as easy as restarting the transaction every now and then > > -- > Laurent "ker2x" Laborde > Sysadmin & DBA at http://www.over-blog.com/ > _______________________________________________ > Neo mailing list > [email protected] > https://lists.neo4j.org/mailman/listinfo/user >
-- Mattias Persson, [[email protected]] Neo Technology, www.neotechnology.com _______________________________________________ Neo mailing list [email protected] https://lists.neo4j.org/mailman/listinfo/user
