Nonetheless, isn't it a MySQL feature that the first timestamp field in a record that is not specified in an UPDATE (or has the value NULL specified) is automagically updated with the current timestamp?
I usually have a timestamp field named "updated" as the first timestamp field in a table layout just for that reason.
You can avoid this behaviour by adding (assuming your field name is "datum") datum=datum to your UPDATE statement. Looks funny, but it works for me.
Hope this helps.
Liz
In reply to Re: Bug on MySQL? timestamp problem
by liz
in thread Bug on MySQL? timestamp problem
by kidd
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |