Standard PK generation is based on EOF keeping track of the last used value.
This last used value will always be counted up, never down. This insures that
no value will ever be re-used. The bookkeeping happens in two different ways,
depending on the database system. Many database systems provide
Hi there,
presumed I use integer PKs and don't ever assign them myself, leaving it on
EOF, can I rely on that never a newly created EO would get same PK as used to
have one deleted previously? Or is there some rare scenario when this may
happen?
I need to store some information for EOs (which
In memory you will have a temporary ID and it doesn’t seem possible to
interfere or duplicate in any practical sense, it’s local.
Once stored in the DB it will have a key, which is generally tied to a
“by-hand” method of generation, but I think everyone accepts that who uses EOF
and I don’t see
