Is a set current TIMESTAMP operation atomic when updating/inserting multiple rows?

2006-07-23 Thread Dan Jakubiec
Hi. I want to insert/update multiple rows into a table which has a timestamp field, and I want to set the timestamp field in each row to the current timestamp. However, it is important to me that all the rows I update actually end up with the same timestamp value. My concern is: what happens

Re: Is a set current TIMESTAMP operation atomic when updating/inserting multiple rows?

2006-07-23 Thread Chris W
Dan Jakubiec wrote: Hi. I want to insert/update multiple rows into a table which has a timestamp field, and I want to set the timestamp field in each row to the current timestamp. However, it is important to me that all the rows I update actually end up with the same timestamp value. My

Re: Is a set current TIMESTAMP operation atomic when updating/inserting multiple rows?

2006-07-23 Thread Dan Jakubiec
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()'

Re: Is a set current TIMESTAMP operation atomic when updating/inserting multiple rows?

2006-07-23 Thread Dilipkumar
mysql@lists.mysql.com Sent: Monday, July 24, 2006 1:11 AM Subject: Re: Is a set current TIMESTAMP operation atomic when updating/inserting multiple rows? Dan Jakubiec wrote: Hi. I want to insert/update multiple rows into a table which has a timestamp field, and I want to set the timestamp