Bug #20882 Reverse Engineering creates wrong default values
Submitted: 6 Jul 2006 6:33 Modified: 6 Jul 2006 11:58
Reporter: Bruno Baketaric Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Workbench Preview Severity:S3 (Non-critical)
Version:1.1.1-alpha OS:Windows (WinXP)
Assigned to: CPU Architecture:Any

[6 Jul 2006 6:33] Bruno Baketaric
Description:
Reverse engineering (a set of InnoDB tables in my case) creates default values '0'  (with quotes) for int() columns. Should'nt this be just 0 (without quotes)?

How to repeat:
Create a InnoDB Table with some int() columns, default 0. Reverse engineer it. Defaul values appear as '0' in table editor.
[6 Jul 2006 11:58] MySQL Verification Team
Thank you for the bug report. The quoted 0 ('0') is a valid
syntax accepted by the server:

c:\mysql\bin>mysql -uroot test
Welcome to the MySQL monitor.  Commands end with ; or \g.
Your MySQL connection id is 1 to server version: 5.0.22-community-nt

Type 'help;' or '\h' for help. Type '\c' to clear the buffer.

mysql> create table ht (id int not null default '0', name char(10));
Query OK, 0 rows affected (0.44 sec)

mysql> insert into ht (name) values ('mary');
Query OK, 1 row affected (0.25 sec)

mysql> select * from ht;
+----+------+
| id | name |
+----+------+
|  0 | mary |
+----+------+
1 row in set (0.08 sec)

mysql>