David,
I could be wrong but since bigint isn't a date or time oriented data
type I imagine this would be completely useless to you unless you are
storing unix timestamps. You also have the option of using datetime data
types. I'm not quite sure what you are asking nor what difference it makes
how big the field is in bytes. Timestamp and Datetime are pretty much the
same except the first timestamp field of every row will automatically be
"timestamped" when you do update's or inserts with a null value in the
field.
Ric.
----- Original Message -----
From: "David BORDAS" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, April 09, 2002 10:04 AM
Subject: TIMESTAMP(14) or Bigint ??
> Hi,
>
> i'd like to alter a table which have a date and time field so 3 Bytes for
> date and 3 Bytes for time.
> I'd table to add a new field to store date like this : YYYYMMDDHHMMSS.
>
> In fact, I can't use indexes on sql query like select with order by with 2
> fields date + time and with
> one unique field i can.
>
> So, for this new field that i'll insert and update manually, should i use
a
> Bigint which required 8 Bytes or a Timestamp(14) with 4 Bytes ?
>
> Timestamp looks great but, can i insert and update it manually ??
>
> Thanks
> David
>
>
>
> ---------------------------------------------------------------------
> Before posting, please check:
> http://www.mysql.com/manual.php (the manual)
> http://lists.mysql.com/ (the list archive)
>
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
>
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
