On Wed, 16 Sep 2009 07:35:55 -0400, Denis Gäbler wrote: >>Some sub-systems have an implicit COMMIT at end of programme.
>And this for a very good reason, or would you like your programmer to decide >whether to commit or rollback if an unexpected error occurs and let them ruin >your databases data integrity? >What if the error is such as that the program will never receive control? Who >will then issue the commit or rollback or set the return code? > I take the opposite view: If no COMMIT is issued, the database remains in its prior state, and its integrity is undamaged. Default ROLLBACK is the safer design. Surely programmers don't issue COMMIT when the database is in an inconsistent state. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
