Re: TimeStamp Problem

[broehmer@xxxxxxxxxxxxxxx]

We're on 6.1 hopefully moving to 7.1 before end of summer.

To answer your question....it's an old file that is more or less for
historical purposes.  Not a real problem yet but we were trying
to solve a "last record" for a group problem and ran into duplicates
using SQL.
Not a show stopper but close.


Bill 

"CONFIDENTIALITY NOTICE:  This e-mail transmission (and/or the attachments 
accompanying it) contain confidential information belonging to the sender. 
 The information is intended only for the use of the intended recipient. 
If you are not the intended recipient, you are hereby notified that any 
disclosure, copying, distribution or the taking of any action in reliance 
on the contents of the information is strictly prohibited.  Any 
unauthorized interception of this transmission is illegal under the law. 
If you have received this transmission in error, please promptly notify 
the sender by reply e-mail, and then destroy all copies of the 
transmission."






From:   Alan Campin <alan0307d@xxxxxxxxx>
To:     Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date:   04/16/2015 04:49 PM
Subject:        Re: TimeStamp Problem
Sent by:        "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Depends what release you are. The more current releases have more
precision. Why are you using a timestamp for a unique value. Why not use 
an
identity key?
On Apr 16, 2015 3:16 PM, <broehmer@xxxxxxxxxxxxxxx> wrote:

> All right.  I'm going to ask one of those "stupid" questions.
>
> Why does the time stamp only use the first 3 positions of the 
millisecond?
> We just tried to find unique records for a file based on time stamp and
> got
> several results returned all with the last 3 positions 0. In fact, all 
our
> files
> are like that.
>
> Is this by design? Are we doing something wrong when we write them out?
>
>
>
> Bill Roehmer
>
>
> "CONFIDENTIALITY NOTICE:  This e-mail transmission (and/or the 
attachments
> accompanying it) contain confidential information belonging to the 
sender.
>  The information is intended only for the use of the intended recipient.
> If you are not the intended recipient, you are hereby notified that any
> disclosure, copying, distribution or the taking of any action in 
reliance
> on the contents of the information is strictly prohibited.  Any
> unauthorized interception of this transmission is illegal under the law.
> If you have received this transmission in error, please promptly notify
> the sender by reply e-mail, and then destroy all copies of the
> transmission."
>
>
>
>
> "CONFIDENTIALITY NOTICE:  This e-mail transmission (and/or the 
attachments
> accompanying it) contain confidential information belonging to the 
sender.
> The information is intended only for the use of the intended recipient. 
If
> you are not the intended recipient, you are hereby notified that any
> disclosure, copying, distribution or the taking of any action in 
reliance
> on the contents of the information is strictly prohibited.  Any
> unauthorized interception of this transmission is illegal under the law.
> If you have received this transmission in error, please promptly notify 
the
> sender by reply e-mail, and then destroy all copies of the 
transmission."
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing 
list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.