Re: timestamp field not operated right

[peterlaursen]

one comment to that …

with the INSERT and UPDATE statement it is only the FIRST timestamp field in the table that is effected.

Very often you'd like to have a timestamp showing record_create_time and another showing record_update_time.

If there is a change in data in some other colums and the UPDATE does not reference the first (and only that) timestamp field, then the first will be updated with current time.

Setting ALL timestamps defined with “NOT NULL” to NULL would update both and I don't like that!

But as much flexibility as possible without too much “fuzz” … 🙂