| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
 |
 | |||
| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
|
| |||
Home -> Community -> Mailing Lists -> Oracle-L -> RE: TRIGGERS
JK,
Have you read anything about PL/SQL generally and triggers specifically?
Someone earlier mentioned you may have a design issue here, and I would = agree with that. You might consider rethinking what you are doing.
-----Original Message-----
From: oracle-l-bounce_at_freelists.org
[mailto:oracle-l-bounce_at_freelists.org]On Behalf Of Kean Jacinta
Sent: Wednesday, May 18, 2005 10:34 AM
To: oracle-l_at_freelists.org
Subject: Re: TRIGGERS
HI,
here is what i have written in trigger body, i am really stuck here. help me up , it;s still not working . System still complain about the unique key error. **:(
DECLARE
REFCOUNT NUMBER;
DUP_VAL_ON_INDEX EXCEPTION;
TEMP NUMBER;
LOOP =20
SELECT COUNT(*) INTO REFCOUNT
FROM myclass
WHERE :NEW.id =3D id;
=20
IF REFCOUNT > 0 THEN --RECORD EXISTED IN
DATABASE
SELECT myclass_seq.NEXTVAL INTO TEMP FROM DUAL;
END IF;
=20
=20
END LOOP; =20
=20
IF :NEW.ID IS NULL THEN
=20
=20
SELECT myclass_SEQ.NEXTVAL=20
INTO :NEW.ID=20
FROM DUAL;
END IF;
=20
JKean
> If you really want to handle that, you have three > choices: >=20 > 1) Live with it. If you have a program that > assigns the id values for you, it should be getting > its next value from the sequence also. If you do > that, this just isn't a problem in real life. If > you aren't willing to ALWAYS get the next id value > from a sequence, you probably shouldn't be using a > sequence at all. >=20 > 2) Relatively simple, partial solution. Use a > pre-statement trigger on insert, have it grab the > next sequence value and verify that the record for > that sequence number is not already in the table.=20 > If it is, get the next sequence value until you find > an empty one. Assume that all the ones after that > are ok from then on. Ignore the fact taht you throw > away a sequence number each time you do a statement. > Remember, I said *partial* solution. >=20 > 3) Read up on mutating table errors and autonomous > transactions. This will take you awhile to read and > experiment with. We have time to help with specific > problems, but not to write it for you. > Ask again after you've read that material and are > are stuck. >=20 >=20 >=20 > -----Original Message----- > From: Kean Jacinta <jacintakean_at_yahoo.com> > Sent: May 18, 2005 8:02 AM > To: david wendelken <davewendelken_at_earthlink.net> > Subject: Re: TRIGGERS >=20 > david, >=20 > :P oh i see . I am so blur. My concern, >=20 > ID =20 > --- > 1 <-- autogenerated > 2 <-- autogenerated > 3 <-- autogenerated > 4 <-- manually created > 5 <-- manually created=20 >=20 > My current sequence stay at : 3 , if i issued an > autotgenerated insert again it will surely prompt > unique id alrdy existed... or some sort of database > error. How can then trigger being smart enough to > silently generate autoid 6 without raising error ? >=20 > I am very close to my objectives alrdy :P >=20 > Thank in advance > Jkean=20 >=20 =09 __________________________________=20
-- http://www.freelists.org/webpage/oracle-l This electronic message transmission is a PRIVATE communication which = contains information which may be confidential or privileged. The information is = intended=20 to be for the use of the individual or entity named above. If you are = not the=20 intended recipient, please be aware that any disclosure, copying, = distribution=20 or use of the contents of this information is prohibited. Please notify = the sender of the delivery error by replying to this message, or notify us = by telephone (877-633-2436, ext. 0), and then delete it from your system. -- http://www.freelists.org/webpage/oracle-lReceived on Wed May 18 2005 - 12:49:15 CDT
 |
 |