|
Thanks for keeping me honest! I'd
forgotten that MySQL timestamps don't keep the fractional parts of seconds
either; I mostly use DB2 which keeps the fractional parts (microseconds) and
forgot about this quirk of MySQL.
--
Rhino
----- Original Message -----
Sent: Thursday, March 02, 2006 1:42
PM
Subject: Re: TimeStamp issue
In fact, no time values in
MySQL are fractional (yet). All times are stored to the nearest second
regardless of which date-time-like storage type you use. They way Rhino
phrased his answer, it sounded as though TIMSTAMP would save fractional
seconds. It doesn't. He is spot on about needing a separate column to store
any values that represent fractions of seconds.
Shawn Green
Database Administrator
Unimin
Corporation - Spruce Pine
"Rhino" <[EMAIL PROTECTED]> wrote on
03/02/2006 01:25:36 PM:
> If you need a broader range of dates, you
could use DATETIME instead of
> TIMESTAMP: DATETIME can handle the
range '1000-01-01 00:00:00' through
> '9999-12-31 23:59:59'. The only
big difference is that DATETIME does not
> store the fractional part of
the seconds, e.g.
> milliseconds/microseconds/nanonseconds. If you have
to keep the fractional
> part of the seconds, you could store them in a
second column defined as some
> kind of integer.
>
>
--
> Rhino
>
> ----- Original Message -----
> From:
"rtroiana" <[EMAIL PROTECTED]>
> To:
<mysql@lists.mysql.com>
> Sent: Thursday, March 02, 2006 10:10
AM
> Subject: TimeStamp issue
>
>
> > Hi
All,
> >
> >
> >
> > I have recently
noticed in the MySQL 5.0 documentation in section 11.3.1.
> > The
DATETIME, DATE, and TIMESTAMP Types, it's mentioned that
> >
>
>
> >
> > "TIMESTAMP values cannot be earlier than 1970
or later than 2037. This
> > means
> > that a date such as
'1968-01-01', while legal as a DATETIME or DATE value,
> > is not
valid as a TIMESTAMP value and is converted to 0."
> >
>
>
> >
> > Is that a correct range for TimeStamp? It's not
big enough to be used in a
> > real life application.
>
>
> >
> >
> > I plan to use DATETIME instead of
TIMESTAMP. I used to use
> > "CURRENT_TIMESTAMP on update
CURRENT_TIMESTAMP" as default value for my
> > TimeStamp column. Is
there a way to assign default value to a DateTime
> > column, since I
couldn't find that in the documentation?
> >
> >
>
>
> > Thanks,
> >
> > Reema
> >
>
>
> >
> >
>
>
>
--------------------------------------------------------------------------------
>
>
> No virus found in this incoming message.
> Checked by
AVG Free Edition.
> Version: 7.1.375 / Virus Database: 268.1.1/272 -
Release Date: 01/03/2006
>
>
>
> --
> No
virus found in this outgoing message.
> Checked by AVG Free
Edition.
> Version: 7.1.375 / Virus Database: 268.1.1/272 - Release
Date: 01/03/2006
>
>
> --
> MySQL General Mailing
List
> For list archives: http://lists.mysql.com/mysql
> To
unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
>
No virus found in this incoming message.
Checked by AVG Free
Edition.
Version: 7.1.375 / Virus Database: 268.1.1/272 - Release Date:
01/03/2006
|
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.375 / Virus Database: 268.1.1/272 - Release Date: 01/03/2006
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
