|
Let's say your original application did not use commitment control (don'tThat is a very optimistic view; it assumes that every database update is committed immediately. As soon as you have a transaction that consists of more than one update (isn't that what commitment control is for?) you cannot do the commit from within the subprocedure. Ergo, the caller of the subprocedures has to do the commit.
know why anyone would do that, but that's another topic). Your boss tells
you to implement commitment control on the application. Guess how many
places you need to deal with it? One.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.