|
What's a missing autonumber. If the field is
autonumbered it should always get a number. Could it be that it appears
numbers are skipped?
That could happen if someone enters a row, then deletes
it.
If this is the case and you don't want any skipped numbers you
could re-autonum before each entry.
sel max(col_name) into maxno from table
autonum col_name in table using (maxno+1) 1 nonum
Bernie Lis
----- Original Message -----
Sent: Monday, July 14, 2003 10:18
AM
Subject: [RBASE-L] - An autonumber
trigger?
Has anyone done this? A client has decided
they don't like
the missing autonumbers. I have code to make sure a
unique
number is assigned -- that's not a problem. But I
was
wondering if there's a way to do it with a trigger, either
a before
or an after trigger.
The problem is that the column is a primary
key. That means
it cannot be null. I was thinking of an 'after'
trigger
where the row is added, and then afterwards the row is
updated
with the correct number. But it couldn't be added
with a null in the
column because the PK would be violated.
I could let it assign an
autonumber, then do an update with
the 'correct' number but I would run the
risk that the update
would be to a number higher than the autonumber and
somewhere
down the line they wouldn't be able to add a new record
with
the same autonumber (sorry, do you get that?)
I'm trying to avoid
putting code everywhere that they might
be adding a row into this table,
plus I know they put rows
in from the r>
prompt.
Karen
|
