Developer queston about DB2 transactions

srp · #1 (**permalink**) 10-16-03, 14:29

A developer recently asked me ...

Some transacted database systems have the ability to take a handful of SQL statements, excersise them in order without checking constraints until all of the statements have been evaluated. Thus if you update a row to a row that already exists (key fields) and then delete the row that previously existed it results in an update that is not invalid. Confusing, I know. Can DB2 facilitate this kind of behavior? What is the technical term for this process?

Brett Kaiser · #2 (**permalink**) 10-16-03, 16:19

Quote:

Originally posted by srp
What is the technical term for this process?

A lie...

all transactions within their scope must conform to all constraints...

chuzhoi · #3 (**permalink**) 10-16-03, 20:08

I think it can be called deffered constraint checking. And no, it's not supported by DB2. I mean after set integrity off, no inserts is allowed

As far as I remember, you can do someting like this in Oracle

-dmitri

blom0344 · #4 (**permalink**) 10-17-03, 05:32

Yep, ORACLE allows this by validating at commit time instead of transaction time.

Brett Kaiser · #5 (**permalink**) 10-17-03, 13:04

Quote:

Originally posted by blom0344
Yep, ORACLE allows this by validating at commit time instead of transaction time.

Really? It's not a server setting?

sathyaram_s · #6 (**permalink**) 10-21-03, 04:00

Brett, you were absolutely right in saying 'all transactions within their scope must conform to all constraints...' ...

But the original question, seems to say that all SQL Statements are within the same UOW ...

Cheers
Sathyaram

Quote:

Originally posted by Brett Kaiser
Really? It's not a server setting?

Internet Services

Web Development

Digital Marketing

Consumer Tech