× 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.


  • Subject: Re: Timestamps
  • From: "David Morris" <dmorris@xxxxxxxxxxxxx>
  • Date: Tue, 21 Nov 2000 12:34:52 -0700

Ron,

Why does it have to be that accurate?  It is difficult to set a timestamp in a 
trigger  
to the full precision allowed.  As this is an update, it is obviously not being 
used as a 
unique key field.  By the time you get a full length timestamp in a trigger and 
set your 
update time, it won't be the actual update time anyway.  I would think you 
would be 
just as well off to add .000001 to the time, assuming this is occurring in one 
process.

David Morris

>>> ron.klein@brctsg.com 11/21/00 11:26AM >>>
Hi All,

We have a trigger program which updates a timestamp field in the data file
with the last changed time.  When a commit is done and 3 records are
committed to the same file, all 3 have the same timestamp.  How do I
retrieve the system time with the milliseconds in it?

Thanks

Ron


+---
| 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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.