RE: Timestamp field

[Buck Calabro <buck.calabro@xxxxxxxxxxxxxxxxx>]

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

> -----Original Message-----
> From: zylka.marc@westpoint-stevens.com 
> Sent: Thursday, January 20, 2000 2:22 PM
> To:   RPG400-L@midrange.com
> Subject:      Timestamp field
> 
> Using RPG/IV on V4R1, we are filling a field declared as type timestamp
> using
> the following:
> 
> C       time        qhtmsp
> 
> This line of code does not set the last 3 digits of the field, they are
> 000. 
> This is causing
> a duplicate timestamp in the file when we'd like for it to be unique.  Is
> there
> anything else 
> that does besides moving a 3 digit sequence number to it?
> 
> TIA,
> Marc Zylka
> 
+---
| 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
+---