> I have set up a new production application that uses user sequences
> for the work/job numbers. The groups that use these need to use all of
> the job numbers and are very concerned when the job numbers jump/skip
> for no apparent reason.
One way to cut down on skipping is to apply the sequence number when the
application performs the insert. If your application posts the data as
the job is created, this might not work. But if your application allows
the user to enter the information, then posts and commits when the user
is finished, you could apply the sequence at insert time [INSERT INTO
TABLE VALUES (JOB_SEQ.NEXTVAL, ITEM1, ITEM2, ...); COMMIT;]
The disadvantage to this is that the user cannot reference the job
number until after the job has been committed to the database.
Received on Sat Apr 03 1999 - 20:07:08 CST
