Re: The age-old database design question - Integers or GUID/UUID for primary keys ? What are your thoughts ?

Yep, that's what I used to do on IBM i when I needed to insure uniqueness.

We used an incrementing data area that would get locked when uniqueness was required.

However that does not work so well on other platforms like MySql or Postgres.

Regards,
Richard Schoen
Web: http://www.richardschoen.net
Email: richard@xxxxxxxxxxxxxxxxx
----------------------------------------------------------------------
message: 1
date: Mon, 14 Dec 2020 13:14:10 -0800
from: "James H. H. Lampert" <jamesl@xxxxxxxxxxxxxxxxx>
subject: Re: The age-old database design question - Integers or
GUID/UUID for primary keys ? What are your thoughts ?

On 12/14/20 10:37 AM, Peter Dow wrote:

Pre-checking for existence doesn't always work. If you have a bunch of
jobs adding to the file at the same time, there's a pretty good chance
that between the time you pre-check and when you write the record,
that some other job may beat you to the write.

So have your identifier factory set up in such a way that calling it puts an exclusive lock on something, that the calling program then has to explicitly release once the new record has been written.

--
JHHL