Mikhail, ----- Original Message ----- From: "Mikhail Entaltsev" <[EMAIL PROTECTED]> To: "Heikki Tuuri" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]> Sent: Monday, October 21, 2002 1:11 PM Subject: Timestamp field in the InnoDB table
> Hi, > > I have found one unclear place for me regarding to the timestamp field in > the InnoDB table. > Please, explain me am I correct or not. > > Let's say we have a table Test with 'timestamp' field: > > CREATE TABLE `Test` ( > `id` int(3) NOT NULL auto_increment, > `UpdateDate` timestamp(14) NOT NULL, > PRIMARY KEY (`id`) > ) TYPE=InnoDB; > > and I try to update one row in this table: > > update Test set UpdateDate = NULL where id = 1; > > Let's say I started 'update' statement at 15:00:00. But the row with id = 1 > is blocked by another transaction, > so 'update' statement needs to wait till the end of the transaction. > After 10 sec the block on the record with id = 1 is released. So my 'update' > finished. > > select UpdateDate from Test where id = 1 > > gives me 20021021150000, but I would expect 20021021150010. > > So what do you think about it? looks like the MySQL interpreter assigns the clock time value to the timestamp field before calling the InnoDB backend. Is this a big problem? > Thanks in advance. > > Best regards, > Mikhail. Regards, Heikki > sql, query > --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
