Commitment control, rollback capability, etc all sound good but think of
this scenario:

You run a large sql update which posts a transaction file into the item
master file. As part of this update it updates the quantity on hand in
the item master.

Item Quantity
X 100
X 200

Now let's say someone is running some inventory transaction and it updates
the quantity also
X 205

Can you really notice "Aw shucks, I forgot the WHERE clause on my sql
statement. I'll just do a ROLLBACK."? What happens to the quantity of X?
It's not like it changes it from 205 to 105.

I do agree that journalling is important. I argued for it for years. They
put it off until we got Mimix. Now they've gone gonzo with journal
receivers. Not that Mimix requires such retention. The developers just
love the history and tracking so they make sure the retention is long
enough to always span two month ends. (77 days or some such thing).

Rob Berendt

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by 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].