Maybe he should have tested his SQL statement first.

Jim Horn

message: 4
date: Fri, 21 Aug 2009 06:36:56 +0200
from: "Birgitta Hauser" <Hauser@xxxxxxxxxxxxxxx>
subject: AW: Modernizing applications


some years ago we had to pay a lot of money, because of the lack of
journaling and commitment control (and because my colleague did not save
data before updating them with SQL).

Friday evening, 5.30 pm we were already prepared for the week-end. Then a
client called! "Could you please remove these blabla records from my stock
of inventory."
No problem, my colleague logged in and typed the SQL statement, but missed
something or wrote > instead of < or something like this. Immediately
pressing enter he saw his mistake, but even though he cancelled the query
immediately a few hundred rows were deleted.

... the only way to restore the data was to take stock! Fortunately it was
Friday and the client normally did not work at the week end!
... but in either way we had to pay for the stocktaking (which was not

With journaling and commitment control, the data could have been resettet
with a simple ROLLBACK.

Mit freundlichen Gr??en / Best regards

Birgitta Hauser

This email is intended only for the person or entity
to which it is addressed and may contain information
that is privileged, confidential or otherwise protected
from disclosure. If you are not the named addressee
or an employee or agent responsible for delivering
this message to the named addressee, you are not
authorized to read, print, retain copy, and disseminate
this message or any part of it. If you have received this
message in error please notify us immediately by email,
discard any paper copies and delete all electronic files
of this message.

This thread ...


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

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