Bug #31655 | TIMESTAMP DDL not working as shown in manual | ||
---|---|---|---|
Submitted: | 17 Oct 2007 1:42 | Modified: | 17 Nov 2007 6:51 |
Reporter: | Peter Breyfogle | Email Updates: | |
Status: | No Feedback | Impact on me: | |
Category: | MySQL Server: DDL | Severity: | S1 (Critical) |
Version: | 5.0 | OS: | Windows (Vista Premium) |
Assigned to: | CPU Architecture: | Any |
[17 Oct 2007 1:42]
Peter Breyfogle
[17 Oct 2007 6:51]
Valeriy Kravchuk
Please, specify the exact version, 5.0.x, and complete statement you had used. The problem, if any, is not in that column: C:\Program Files\MySQL\MySQL Server 5.0\bin>mysql -uroot -proot -P3308 Welcome to the MySQL monitor. Commands end with ; or \g. Your MySQL connection id is 5 Server version: 5.0.44-enterprise-gpl-nt-log MySQL Enterprise Server (GPL) Type 'help;' or '\h' for help. Type '\c' to clear the buffer. mysql> use test; Database changed mysql> CREATE TABLE member ( -> ts TIMESTAMP DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP); Query OK, 0 rows affected (0.36 sec) So, it works, as you can see.
[18 Nov 2007 0: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".