NOT REALLY BIG PROBLEM BUT,
WHEN YOU DESIGN A TRIGER IN ORDER TO HANDLE A SEQUENCE YOU SHOULD HAVE IN MIND THAT ALL THE APPLICATIONS WILL USE THE RETURNING VALUE FROM THIS TRIGER (IN ORDER TO AVOID THE GAPS).
CONSIDER THIS:
YOU NEED TO INSERT A NEW LINE FROM SQL.PLUS FOR EXAMPLE:
-YOU ALREADY HAVE A SEQUENCE FOR THIS TABLE :
"emp_seq.nextval".
(assume the triger uses the same sequence)
IF YOU DO NOT use the above triger THIS LINE SOULD BE OK:
insert into emp(empno,ename) values(emp_seq.nextval,'name');
BUT THE SAME TIME THE VAULE FROM THE TRIGER INSTREASED. SO NEXT TIME YOU WILL USE YOUR PHP PAGE USING THE TRIGER YOU WILL HAVE A
emp_seq.nextval+2
IN ORDER TO AVOID THIS YOU SHOULD CREATE AN ANONYMOUS BLOCK IN THE SQL/PLUS TO OBTAIN THE VALUE FROM THE TRIGER.
Brett Stimmerman wrote:
I havne't actually played with it yet, too busy. Why will it cause problems?