Re: DB2 for i, Isolation Level = *NONE, and ACID assumptions vs. other DBs

On Tue, Jul 21, 2009 at 20:53, Charles Wilt<charles.wilt@xxxxxxxxx> wrote:

Both the developer and the DBA are confused by this, their first comments..
"Doesn't DB2 guarantee ACID compliance?"
"In every other db, a single statement like the above is done Atomically."

Yeah, the i is kind of weird when it comes to this. Especially because
there's still lots of code out there that doesn't utilize commitment
control.

But it's not an issue - you can change the default level using
SET OPTION

And yeah - it is extremely irritating if you see people and software
still not running fully transaction aware and without commitment
control, dealing with important production data. It took me quite a
bit of time to get used to the idea that there are still many IT
people stuck in the 80ies.