×
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.
I second that, although I did implement that here, but with code to check for the
duplicate and increment microseconds as needed to get a unique value.
-----Original Message-----
From: RPG400-L [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Luis Rodriguez
Sent: Wednesday, July 15, 2015 11:59 AM
To: RPG programming on the IBM i (AS/400 and iSeries)
Subject: Re: duplicate key error in identity column
Dale,
Personally, I would advise against using a timestamp as a unique key field.
If either the program and/or the box is fast enough a timestamp can be duplicated across consecutive records.
Regards,
Luis
Luis Rodriguez
IBM Certified Systems Expert — eServer i5 iSeries
As an Amazon Associate we earn from qualifying purchases.
This thread ...
Re: duplicate key error in identity column, (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
