|
CheersMessage from Terrence Enger <tenger@xxxxxxxxxxxxxxxx> on Thu, 17 Jul 2008
Greetings,
I am almost scared to contribute again to a thread which has generated
so much heat. No doubt I shall be sorry. Still, here goes ...
Much of the intervening discussion seems to me to be talking about
issues which are, viewed from 50,000 feet, implementation details.
Nowhere in the discussion have I seen any mention of what I think is the
one important item which makes DB2/400 the odd-man-out in the DB2
family:
DB2/400 exposes uncommitted changes to all users of the database.
Comments? (I am going off now to look for my asbestos underwear.)
Cheers,
Terry.
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.