----- "Sean Allen" <
[hidden email]> wrote:
| i assume auto abort does an abort from time to time so that
| transactions dont back up if you leave gemtools open and connected.
|
| is that correct? if yes, how often does it do an abort?
Sean,
autoAbort, is an extension of autoCommit. With autoCommit, a commit is done at the end of each command (menu picks/doits). With autoAbort, an abort is done before the command is executed and a commit is done at the end.
It's main utility is when there are multiple users sharing the same data base, since the abort means that you can pretty much avoid commit conflicts when editting code.
autoAbort is a little odd (right now) if you open a debugger:
1. abort
2. execute code that starts updating persistent state
3. debugger pops up
At this point in time, if you execute a doit or save a method in a browser, the command does an abort which wipes out all of the updates that may have been made by the code up to the moment that the debugger was opened.
It bit me several times when loading Metacello configurations so autoAbort is not turned on by default.
I think in a single user system that autoAbort in conjunction with manual transactions could be very useful ... in between commands the gem would be sitting outside of transaction so you could stay logged into a production system without having an impact ... With that said, I think that a little more work would need to be done on the autoAbort command to make it work correctly in manual transactionmode ....
Dale
Locked
