Re: Problems with timestamp and leap seconds?

2008-03-04 Thread Tim McDaniel
I had a bit of BFOTO and tried simple inserts. mysql create table t (f timestamp); Query OK, 0 rows affected (0.00 sec) mysql insert into t values ('2008-03-04 16:17:00'); Query OK, 1 row affected (0.00 sec) mysql select * from t; +-+ | f

RE: Problems with timestamp and leap seconds?

2008-03-04 Thread Jay Blanchard
[snip] I had a bit of BFOTO and tried simple inserts. mysql create table t (f timestamp); Query OK, 0 rows affected (0.00 sec) mysql insert into t values ('2008-03-04 16:17:00'); Query OK, 1 row affected (0.00 sec) mysql select * from t; +-+

RE: Problems with timestamp and leap seconds?

2008-03-04 Thread Tim McDaniel
On Tue, 4 Mar 2008, Jay Blanchard [EMAIL PROTECTED] wrote: [snip] I had a bit of BFOTO and tried simple inserts. mysql create table t (f timestamp); Query OK, 0 rows affected (0.00 sec) mysql insert into t values ('2008-03-04 16:17:00'); Query OK, 1 row affected (0.00 sec)

RE: Problems with timestamp and leap seconds?

2008-03-04 Thread Jay Blanchard
[snip] The column type needs to be DATETIME. Thank you for pointing me at TIMESTAMP versus DATETIME. I'll read http://dev.mysql.com/doc/refman/4.1/en/date-and-time-types.html thoroughly when I can. Can you give a little more detail as to why DATETIME is necessary? [/snip] It was much too

RE: Problems with timestamp and leap seconds?

2008-03-04 Thread Tim McDaniel
On Tue, 4 Mar 2008, Jay Blanchard [EMAIL PROTECTED] wrote: It was much too quick a reply on my part but it is my understanding that a TIMESTAMP field is updated according to server time and you cannot actually insert a value. I may be wrong as I have never tested this. Even in pre-4.1