|
We are having a problem here with commit/rollback. In a program with several files under commitment control, the problem occurs when the program aborts. Can anyone tell me what happens if the commit or rollback commands are not issued prior to signing off? I haven't much experience with this kind of thing and my inquiring minds wants to know. Right now the procedure is to examine the database and manually delete the records that were not committed. but this strikes me as strange. Doesn't the system automatically rollback when you signoff if you haven't committed? Marvin
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.