I am writing a type of message stack that is built while a task is
processing and presented to the user at the end of processing. I do it
using a function like
Logit("Blah, blah, blah");
Which records the SessionID, Sequence and Message, which is presented to
the user in sequence at the end
John Comerford wrote:
Thanks for the replies guys, banging my head against the wall for not
thinking of using an auto increment integer to handle the sequence,
I've got to cut back on those Friday night beers
Okay, color me confused, but what exactly are you wanting to do anyway?
--
Thanks for the replies guys, banging my head against the wall for not
thinking of using an auto increment integer to handle the sequence, I've
got to cut back on those Friday night beers
On 4/17/07, John Comerford <[EMAIL PROTECTED]> wrote:
Hi Folks,
A) One character string contain
On 4/18/07, Tim Lucia <[EMAIL PROTECTED]> wrote:
-Original Message-
From: John Comerford [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 17, 2007 10:50 PM
To: mysql@lists.mysql.com
Subject: Millisecond time stamp
Hi Folks,
I am putting together a table to hold log entries. I was
On 4/17/07, John Comerford <[EMAIL PROTECTED]> wrote:
Hi Folks,
A) One character string contain a string I build with the date and
milliseconds tagged onto the end
b) Two separate fields Field1 TimeStamp Field2 Milliseconds
I am leaning towards approach B, but saying that it's more gut insti
> -Original Message-
> From: John Comerford [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, April 17, 2007 10:50 PM
> To: mysql@lists.mysql.com
> Subject: Millisecond time stamp
>
> Hi Folks,
>
> I am putting together a table to hold log entries. I was going to i
Hi Folks,
I am putting together a table to hold log entries. I was going to index
it on a field with a type of TimeStamp. Unfortunately this will not
suit my needs because I could have more than one log entry per second.
As far as my (limited) knowledge goes I have two options to get around
