×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
