Hi
Your problem lies in your columns. A timestamp field has the special
property of recording when a record is created or modified. However, only
the first timestamp column in a row is treated this way. I hope this helps.
Mike
----- Original Message -----
From: "Dmitry Kosoy" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: June 8, 2003 7:51 AM
Subject: mysql: bug in update (?)
>
> Hi,
>
> I have a table with 2 fields (among others) with type timestamp
("warndate"
> and "date").
> I run the following update: update dbowner where warndate = now().
> This update affects not only on the field "warndate" but on the field
"date"
> as well.
> After it the both fields got the current date and time value.
> I changed the name of field "date" to another and got the same result.
>
> I got the same behavior in many mysql versions include 4.0.12.
>
> Regards,
> Dmitry
>
> --
> MySQL General Mailing List
> For list archives: http://lists.mysql.com/mysql
> To unsubscribe:
http://lists.mysql.com/[EMAIL PROTECTED]
>
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
