Bug #46878 Errors managing default values for columns
Submitted: 24 Aug 2009 7:13 Modified: 4 Nov 2009 16:44
Reporter: Pablo Gomez Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Workbench Severity:S2 (Serious)
Version:5.2.2a OS:Linux (Opensuse 11.1)
Assigned to: Alfredo Kojima CPU Architecture:Any
Tags: column, DEFAULT, regression, schema, table

[24 Aug 2009 7:13] Pablo Gomez 
Description:
When editing a table, trying to modify a Default Value for a Column, some errors raise:

How to repeat:
* On a timestamp column, you cannot enter a valid value. Entering:
 '12/12/2009 00:00:00'
results in a (unusable) value:
 '12/12/2009

that drives into an error when forward engineering to a database.

* Once you have type a NULL default value for a field, it cannot be deleted unless you type something to substitute it.
[24 Aug 2009 8:21] Susanne Ebrecht 
The only valid date format in MySQL is:

2009-12-12

yyyy-mm-dd

Date, Datetime, Timestamp are not able to handle other forms (localised/globalised) here.

Did you use this form or did you try a localised form?
[24 Aug 2009 8:32] Pablo Gomez 
Please have in mind that I am writing a TIMESTAMP value that might also include the hour form:

2009-12-12 12:21:01 

should also be valid.

Using this above form, the results are the same. This is the result as seen in the SQL script to be executed (when forward engineering is invoked):

[...]
  `fechaFinalPublicacion` TIMESTAMP NULL DEFAULT 2009-12-12 COMMENT 'vacio -> sin caducidad' ,
[...]
[24 Aug 2009 13:01] MySQL Verification Team 
Thank you for the feedback. Could you please provide the model project file?. Thanks in advance.
[24 Aug 2009 13:57] Pablo Gomez 
I have uploaded the datamodel file. Hope it helps.

Gracias!
[25 Aug 2009 12:47] Valeriy Kravchuk 
Verified exactly as described with 5.2.2a on Ubuntu 8.04 (with '2009-12-12 00:00:00' as a default value).
[27 Oct 2009 2:33] Alfredo Kojima 
Bug is fixed, it happens with any type of string default values, not only date/time
[3 Nov 2009 16:14] Johannes Taxacher 
fix confirmed in repository. will be included in 5.2.7
[4 Nov 2009 16:44] Tony Bedford 
An entry was added to the 5.2.7 changelog:

In the Table Editor, when trying to modify a column default value, errors occurred.

On a TIMESTAMP column it was not possible to enter a valid value of the format yyyy-mm-dd hh:mm:ss. This caused an error if forward engineering was attempted.

A NULL default value for a column could not be deleted.