Ah, thanks Chris. I should have looked there (I was studying the TIMESTAMP sections, not NOW()). The NOW() documentation also refers to the SYSDATE() function which does the opposite (i.e. sets the time when the record actually gets added).
So I'll go ahead and use the 'my_timestamp=NOW()' format in my queries. Out of curiosity, I wonder which of the two approaches 'my_timestamp=NULL' uses... NOW() or SYSDATE()? -- Dan In the manual it says that all calls to now() in a query always return
the same time regardless of how many there are and how long it takes the query to run so I am thinking that all records with an auto update time stamp column that get changed in a single query would all have the same time stamp. It should be easy enough to test if you have a large set of data where an update would take a long time. I'm pretty sure it will do what you need though and set them all the same.
