On 3/2/06, rtroiana <[EMAIL PROTECTED]> wrote:
> Thanks to all of you for replying. I'm using DATETIME instead of TIMESTAMP
> now. Although I still haven't find the answer for my second question.
>
>
>
> > > I used to use
> > > "CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP" as default value for my
lumn. Is there a way to assign default value to a DateTime
> > column, since I couldn't find that in the documentation?
_
From: Rhino [mailto:[EMAIL PROTECTED]
Sent: Thursday, March 02, 2006 3:50 PM
To: [EMAIL PROTECTED]
Cc: mysql@lists.mysql.com; rtroiana
Subje
PROTECTED]
To: Rhino
Cc: mysql@lists.mysql.com ; rtroiana
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
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 se
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
'-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/nanons
rtroiana wrote:
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 D
At 16:49 +0530 9/17/02, Prafulla Girgaonkar wrote:
>Mysql Version::
>
>Server version 3.23.47-nt
>Protocol version10
>Connection . via named pipe
>UNIX socket MySQL
>
>OS::
>Windows NT 4.0 Workstation
>
>
>Hello
>Following is the description of the problem
Prafulla,
Tuesday, September 17, 2002, 2:12:58 PM, you wrote:
PG> Following is the description of the problem being faced.
PG> Problem:
PG> The first timestamp column in a table is set to current date-time value as soon as
we update one or more columns in the table.
It's a normal behaviour of
Prafulla,
please check documentation http://www.mysql.com/doc/en/DATETIME.html
"...
The TIMESTAMP column type provides a type that you can use to automatically
mark INSERT or UPDATE operations with the current date and time. If you have
multiple TIMESTAMP columns, only the first one is updated au
