Page 1 of 1

Schema Comparison generates invalid sql for DEFAULT CURRENT_TIMESTAMP

Posted: Fri 21 Nov 2014 00:25
by thecodeslinger
Has this been fixed?

To reproduce:
1.

Code: Select all

CREATE TABLE table1 (
  col1 int(11) DEFAULT NULL,
  created datetime DEFAULT CURRENT_TIMESTAMP
)
2. use schema comparison to compare with another database that does not have this table. The following sql is generated. It puts quotes around the CURRENT_TIMESTAMP keyword which is invalid for a DEFAULT.

Code: Select all

CREATE TABLE table1 (
  col1 int(11) DEFAULT NULL,
  created datetime DEFAULT 'CURRENT_TIMESTAMP'
)

Re: Schema Comparison generates invalid sql for DEFAULT CURRENT_TIMESTAMP

Posted: Fri 21 Nov 2014 09:34
by alexa
We will fix this issue in the next product build and will notify you once it's available for downloading.

Re: Schema Comparison generates invalid sql for DEFAULT CURRENT_TIMESTAMP

Posted: Wed 10 Dec 2014 16:13
by alexa
We would like to let you know that we have released a new version 6.3 of dbForge Studio for MySQL where this issue is fixed http://www.devart.com/dbforge/mysql/stu ... nload.html

Thank you for your help in improving dbForge Studio for MySQL.