('val1','PROD1','2005-09-14 15:21:41');
Specifically, the discrepancy appears to be the number of leap seconds
that were in effect at the point of the timestamp. E.g.,
line 697611, characters 15 on:
...sions VALUES ('val2','PROD2','2006-07-31 11:30:57');
...sions VALUES ('val2
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
[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;
+-+
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)
[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
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
the tables and import the tables into the upgraded environment.
You could also export your 4.0.x data and import this data into the newly
created 4.1.3 environment.
-Original Message-
From: Jeff Mathis
To: mysql
Sent: 8/4/04 11:14 AM
Subject: time zone leap seconds
we just upgraded from 4.0.4
we just upgraded from 4.0.4 to 4.1.3, and are getting this warning. is
there a script somewhere we can run to create the alleged missing time
zone table?
040804 10:09:49 Warning: Can't open time zone table: Table
'mysql.time_zone_leap_second' doesn't exist trying to live without them
thanks
To: mysql
Sent: 8/4/04 11:14 AM
Subject: time zone leap seconds
we just upgraded from 4.0.4 to 4.1.3, and are getting this warning. is
there a script somewhere we can run to create the alleged missing time
zone table?
040804 10:09:49 Warning: Can't open time zone table: Table
matt,
Tuesday, March 19, 2002, 8:31:08 AM, you wrote:
Try to install the official MySQL binary distribution (3.23.49a) from
www.mysql.com and check timestamp there. There was some bugs about
timezones in old version of MySQL/glibc.
mDescription:
m A timestamp value selected back is 38
Correct me if I'm wrong, but a timestamp field is not meant to be human
updateable (ie. it's solely to record the last change to the record).
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 19, 2002 1:31 AM
To: [EMAIL PROTECTED]
Subject: Leap
Description:
A timestamp value selected back is 38 seconds later than what
was inserted.
How-To-Repeat:
ln -s /usr/share/zoneinfo/right/US/Pacific /etc/localtime
mysql test
mysql create table teststamps (stamp timestamp);
mysql insert teststamps
12 matches
Mail list logo
