mysql default value
Posted: Mon Nov 30, 2015 11:21 amI can't reproduce that.
Are you just setting new default value to "CURRENT_TIMESTAMP" (without quotes)?
Page 1 of 1
Posted: Mon Nov 30, 2015 11:21 amRe: mysql default value
Posted: Tue Dec 01, 2015 10:22 amRe: mysql default value
Posted: Wed Dec 09, 2015 2:32 pmYes serge i'm sure. My value CURRENT_TIMESTAMP. My charset Turkish, this problem for default value ?
Re: mysql default value
Posted: Wed Dec 09, 2015 2:47 pmI don't think that it can be somehow related to charset.
Just in case - could you try to run DBeaver with parameter "-nl en" and check this issue again?
Also, check it in the recent version (3.5.6). There were some fixes related to default values.
Just in case - could you try to run DBeaver with parameter "-nl en" and check this issue again?
Also, check it in the recent version (3.5.6). There were some fixes related to default values.
Re: mysql default value
Posted: Thu Dec 10, 2015 10:21 amI can confirm this bug. DBeaver will put CURRENT_TIMESTAMP in single quotes and MySQL will treat it as a string not a special timestamp default value.
Re: mysql default value
Posted: Thu Dec 10, 2015 11:36 amRe: mysql default value
Posted: Thu Dec 10, 2015 1:53 pmI did reproduce that (at least for new columns).
Fix will be added in the next version.
Thanks for report!
Fix will be added in the next version.
Thanks for report!