You are viewing a plain text version of this content. The canonical link for it is here.
Posted to ddlutils-dev@db.apache.org by "Thomas Dudziak (JIRA)" <ji...@apache.org> on 2006/07/30 07:26:15 UTC
[jira] Commented: (DDLUTILS-62) column DEFAULT - SQL error during
create table in ddlToDatabase( to MySQL) using files produced by
databaseToDdl(from MSSQL)
[ http://issues.apache.org/jira/browse/DDLUTILS-62?page=comments#action_12424354 ]
Thomas Dudziak commented on DDLUTILS-62:
----------------------------------------
Could you please attach either the original table's definition SQL, or the schema dumped by DdlUtils?
> column DEFAULT - SQL error during create table in ddlToDatabase( to MySQL) using files produced by databaseToDdl(from MSSQL)
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: DDLUTILS-62
> URL: http://issues.apache.org/jira/browse/DDLUTILS-62
> Project: DdlUtils
> Issue Type: Bug
> Components: Core (No specific database)
> Environment: Windows 2K
> MSSQL 2000
> JDBC Driver - jtds
> MySQL 5.0
> JDBC driver - MySQL Connector/J - mysql-connector-java-5.0.0-beta
> Reporter: Appajee Papolu
> Assigned To: Thomas Dudziak
> Fix For: 1.0
>
>
> - This issue is clone of another issue, but is cloned for highlighting the specific issue around the actual default value
> - Dumped out a database from MSSQL using ddlutils ant task
> - Using these files, attempting creating the equivalent database on MySQL 5.0
> - Getting few errors as below:
> CREATE TABLE `whatever`
> (
> `col1` INTEGER NOT NULL,
> `col2` INTEGER NOT NULL,
> `col3` CHAR(1) DEFAULT '(''some string'')' NULL
> ) failed with You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax ...
> - I changed the col3 line to as follows and then the ddltodatabase works fine
> `col3` CHAR(1) DEFAULT 'some string' NULL
> - I am not too sure why this specific default value is xml encoded in the first place, but in any case, if one indeed had such literal data,
> there should be a way to configure the ddlutils to deal with it (possibly appropriately escape/encode)
> - I could not find info if there were any user configurable settings that can overcome this problem.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira