D
dbeavon
Guest
According to the docs, QUIT commits the current data: Link The faulty data indicates an invalid state going all the way back up to the start of the transaction (potentially many levels up the call-stack, with different possible call-stacks that may reference the procedure). While it is the most common scenario, it isn't always a CHUI client that uses the procedure either - it may be a batch or something else. Redesigning the code would take too much effort, especially considering how rare it is that we get ourselves into an invalid state and create invalid data (once a month or so, on a very busy database). Regardless of the reason, STOP is about as close as the ABL comes to what we are looking to do (ie. rollback and crash out of the AVM). Here is the link to STOP information : I just wish we could prevent any ON STOP handling (as would be the case if we used kill -SIGHUP).
Continue reading...
Continue reading...