×
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.
<Joe>
I disagree with that one. You simply describe the field as a UUID. You'd
then have to go out of your way to tell the auditors that it is sequentially
generated.
</Joe>
UUIDs might have collisions, rather seldom, depending on implementation, but
it could happen! We tested this out, some years ago. Running on AS/400 (the
V5R2 implementation used a combination of MAC adress and timestamp) with
multiple fast processors and heavy transactional, masive parallel workload ,
we've got collisions in every run. More recent implementations are using a
combination of timestamp and some random number, taht's better, but could
produce collisions running on diffrent systems.
D*B
As an Amazon Associate we earn from qualifying purchases.
This thread ...
RE: Identity columns, was: Using long names, (continued)
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
