Bug #28291 Problem with storing data into a datetime column

• Submitted: 8 May 2007 0:28
• Modified: 8 Jun 2007 0:51
• Reporter: Carlos Barboni
• Status: No Feedback
• Category: MySQL Server: Data Types
• Severity: S3 (Non-critical)
• Version: 5.0.32-Debian_7etch1-log Debian etch
• OS: Linux (Etch)
• CPU Architecture: Any

[8 May 2007 0:28] Carlos Barboni

Description:
I have a datetime column, and store this value'2999-12-31 00:00:00', but in a select statment, show: '2999-12-31 00:31:00'

--------------------------------------------------------------------
mysql> create table test (mydate datetime);
Query OK, 0 rows affected (0.01 sec)

mysql> insert into test (mydate) values ('2999-12-31 00:00:00'); 
Query OK, 1 row affected (0.00 sec)

mysql> select * from test;
+---------------------+
| mydate              |
+---------------------+
| 2999-12-31 00:31:00 | 
+---------------------+
1 row in set (0.00 sec)

---------------------------------------------------------------------

How to repeat:
The bug is repeat in all inserts of the table.
I have a table with more than 20.000 records and the datetime column show '2999-12-31 00:31:00' in place of '2999-12-31 00:00:00'

[8 May 2007 0:51] MySQL Verification Team

Thank you for the bug report. Could you please try with latest released
version. I was not able to repeat with current source server:

mysql> select version();
+--------------+
| version()    |
+--------------+
| 5.0.42-debug | 
+--------------+
1 row in set (0.00 sec)

mysql> create table test (mydate datetime);
Query OK, 0 rows affected (0.03 sec)

mysql> insert into test (mydate) values ('2999-12-31 00:00:00'); 
Query OK, 1 row affected (0.01 sec)

mysql> select * from test;
+---------------------+
| mydate              |
+---------------------+
| 2999-12-31 00:00:00 | 
+---------------------+
1 row in set (0.01 sec)

mysql>

[8 Jun 2007 23:00] Bugs System

No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".