Bookmarks

Yahoo Gmail Google Facebook Delicious Twitter Reddit Stumpleupon Myspace Digg

Search queries

sqldatasource dal, wwwxxxenden, convert raid5 to raid 10 mdadm, apache force chunked, nrao wwwxxx, xxxxxdup, procmail change subject header, wwwXxx not20, Wwwxxx.doks sas, linux raid resync after reboot

Links

XODOX
Impressum

#1: problem with timestamp data type

Posted on 2007-05-23 13:32:45 by Alessandro Agostini

Hi to all,
I have a strange error on using of timestamp data type.
See the follow table definition and insert command.

DROP TABLE IF EXISTS Storicocorrenti;
CREATE TABLE Storicocorrenti (
ID_LINEA mediumint(6) unsigned zerofill NOT NULL default '000000',
DATAORA timestamp NOT NULL default '0000-00-00 00:00:00',
DFASEABS smallint(3) default NULL,
TENSIONE decimal(9,2) default NULL,
POTATT decimal(7,3) default NULL,
POTREA decimal(7,3) default NULL,
DFASEVI smallint(3) default NULL,
CORRENTE decimal(6,2) default NULL,
PRIMARY KEY (ID_LINEA,DATAORA)
) ENGINE=MyISAM DEFAULT CHARSET=latin1;

INSERT INTO Storicocorrenti VALUES (032100, '2005-03-27 01:00:00', 0,
'400000.00', '0.000', '0.000', 0, '0.00');
INSERT INTO Storicocorrenti VALUES (032100, '2005-03-27 02:00:00', 0,
'400000.00', '0.000', '0.000', 0, '0.00');

Watching the table content, I see second record as:

032100, '2005-03-27 03:00:00', 0, '400000.00', '0.000', '0.000', 0, '0.00'

MySql change the time information of DATAORA field from "02:00:00" to "03:00:00".

This error is reproducible on various version of mysql. I have tried it on 3.23,
4.1, 5.0

On Postgres DB all is ok. I have similar record at same time but other date and
in these case the problem is not present.

Can you help me to resolve it?
Thanks in advance

Alessandro Agostini
IFAC - CNR
Italy


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Report this message