Re: Timestamp field

Marc,

I have used the timestamp as key by defining a logical file that does
not have the timestamp field in it.  This way, the program writes all
the data fields andthe system defaults to the current time, with all
digits up to the microsecond.  I do not like very much that solution,
but it works fine. 
____________________________________________________________________________
Buck Calabro wrote:
> 
> Marc,
> I would not depend on using the timestamp as a unique key.  As you have
> found out, on a sufficiently fast enough machine you can get duplicates.
> The upshot of this is that even if it works today, when the next generation
> of CPUs come out it might fail.
> 
> I would suggest adding another field (sequence number) if you have a need to
> discriminate between each record.  If you really truly need the extra three
> digits, consider using SQL to do your insert, as in:
> insert into xxx (field, timstp) values(:field, CURRENT TIMESTAMP)
> 
> Buck Calabro
> Aptis; Albany, NY
<snip>
-- 
  Raul A. Jager W.
Asuncion - Paraguay
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---