Timing Issues in Oracle

From: Gordon E. Hooker <gordonh_at_acslink.net.au>
Date: 1995/07/08
Message-ID: <3tlng2$j8g_at_dingo.cc.uq.oz.au>#1/1

Hi All,

I am fairly new to the Oracle fold after many years working with Informix.

I have a question I would like to pose to anyone out there who can advise me.

I would like to know how the Oracle server implements the relational concept of timing with regards to constraint checking.

In a transaction if I wanted to update data on which there is an unique constraint how would you defer the constraint. What I mean is as follows:

I have a set of rows

col1 unique
1
2
3
4
I want to update the table and set col1 = col1 + 1. When the value 1 is update and set to 1+1 it would cause unique constraint error. How could I defer constraint checking until all the rows had 1 added to it, which at the end of the update not cause the error?

Thanks in advance...

-----------------------------\ooOoo/-----------------------------------
Gordon Hooker MACS PCP                                     ,--_|\
25 Clarke Street, Ripley, Queensland, 4306, Australia     /      \ 
gordonh_at_acslink.net.au                                    \_.--._/
mobile: 018883835 phone: 61-7-2889716                           V
-----------------------------------------------------------------------

The opinions you read here are mine and not necessarily those of my employers. Although, I must say they are the truth, the whole truth, and nothing like the truth. As far as I'm concerned anyway... Received on Sat Jul 08 1995 - 00:00:00 CEST