|
On 16-Aug-2014 06:36 -0500, D*B wrote:
On 14-Aug-2014 08:10 -0500, CRPence wrote:A result that is a clear contradiction both to the documentation of the
<<SNIP>> Even if a timestamp with necessary precision is not
guaranteed to be unique, there is of course, for example, the
result of the SQL scalar function GENERATE_UNIQUE() [generates a
UUID] which is a unique value satisfactory for sequencing and that
includes a TIMESTAMP. <<SNIP>>
... a couple of years ago I've evaluated GENUUID on AS/400; the
documentation ended up with "most likely unique" and testing in a
heavy parallel environment brought up collisions; as far as I
remember the implementation did not include the processor number,
with the result of possible duplicate values on multi processor
boxes.
feature and to the /standard/ effect, is IMO, clearly a *defect* that
should be reported. Given the tests were conducted so long ago, there is a
very good chance the feature has been corrected, because someone who had
recognized the contradiction cared enough about proper results [for
themselves and possibly for others] to report the issue.
--
Regards, Chuck
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
As an Amazon Associate we earn from qualifying purchases.
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.