I had a similar issue with importing things into the db (i.e only INSERT/UPDATE instructions).
I kept manual track of what was inserted, which allowed me to rollback the actions on demand - basically that's the command pattern, where all the commands are persisted to the DB, and each command execution is in a single db transaction.
-Michael
On Sat, Nov 7, 2009 at 7:12 AM, Mark Robinson
<mark.robinson@xxxxxxxxx> wrote:
Hey everybody,
We're trying to figure out a good way to use some sort of long transaction system. What we'd like to be able to do is allow users to work with a set of entities for 15-30 minutes and then let them commit the whole process rather than commit each entity separately. Ideally we'd like to be able to save their work part-way through so that it is lost if they lose their connection or their system crashes.
Does anyone have any suggestions on how they would implement something like this?
Mark
--
Mark Robinson, EIT - Mizar LLC
mark.robinson@xxxxxxxxx
111-1010 McKenzie Ave.
Victoria, BC
V8X 4B2
(360) 296-4125
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
