tags 311867 + confirmed wontfix
thanks
Hello
On 2005-06-03 Jacob L. Anawalt wrote:
> When inserting a bad time format, eg 24:00 or 24:30, into MySQL the
> server happily accepts the bad data "Query OK, 1 row affected", and then
> turns the data into garbage "0000-00-00 00:00:00".
For the 4.0 branch, yes, that's sadly so but this release won't be touched
by MySQL for minor bugs any more.
In 4.1 the behaviour has been improved, so you might consider upgrading:
mysql> INSERT INTO t SET d="2005-06-03 24:00:00";
Query OK, 1 row affected, 1 warning (0.06 sec)
^^^^^^^^^^
mysql> SHOW WARNINGS;
+---------+------+------------------------------------------------------+
| Level | Code | Message |
+---------+------+------------------------------------------------------+
| Warning | 1264 | Data truncated; out of range for column 'd' at row 1 |
+---------+------+------------------------------------------------------+
1 row in set (0.00 sec)
bye,
-christian-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
