Consider improving MVCC by providing transaction support that spans multiple collections

[albert-kam]

Migrated from mailing list: https://groups.google.com/forum/#!topic/cqengine-discuss/qwkUy4gPNOo

Is there a way i can do multiple updates to multiple indexedCollections within a single transactional context 'commit' ?

This is to achieve the same goal for consistent read_commited retrievals, only that this commit applies for multiple collections. Either all the updates for all collections are seen or not at all.

For example: // transaction.start(); cars.update(asList(car2), asList(car3, car4)); bikes.update(asList(bike2), asList(bike3, bike4)); // transaction.commit();

Thank you !

[npgall]

Thanks for creating this Albert. As discussed, it's an interesting idea, and I'll investigate adding support for it.