Order of the columns (timestamp) in create statement makes a difference

[Mike Chirico]

The first timestamp will always be "automatically generated time." So if
the record is updated, or inserted, this time gets changed. However, if the
column order is changed with an alter statement, this is no longer the case.

create table t (
a int,
b int,
timeUpdate timestamp,
timeEnter timestamp );

Note above Update and timeEnter, although both are defined as timestamp,
operate differently.
Reference (See TIP 3):
http://unc.dl.sourceforge.net/source...ADME_mysql.txt

I hope this helps...it threw me for a loop the first time.

If you have an interesting TIP can you send it to me or post it? I'll add
to the list to benefit everyone.

Regards,

Mike Chirico

[Leif]

"Mike Chirico" <mc******@comcast.net> skrev i en meddelelse
news:JY********************@comcast.com...

The first timestamp will always be "automatically generated time." So if
the record is updated, or inserted, this time gets changed. However, if the column order is changed with an alter statement, this is no longer the case.
create table t (
a int,
b int,
timeUpdate timestamp,
timeEnter timestamp );

Note above Update and timeEnter, although both are defined as timestamp,
operate differently.

To avoid confusion, only use one timestamp, make the rest datetime

Leif