Mailing-List: contact ddlutils-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ddlutils-dev@db.apache.org
Message-ID: <869416055.1137777342329.JavaMail.jira@ajax.apache.org>
Date: Fri, 20 Jan 2006 18:15:42 +0100 (CET)
From: "Appajee Papolu (JIRA)" <jira@apache.org>
To: ddlutils-dev@db.apache.org
Subject: [jira] Updated: (DDLUTILS-62) CLONE -column DEFAULT - SQL error
 during create table  in ddlToDatabase( to MySQL)  using  files produced by
 databaseToDdl(from MSSQL)
In-Reply-To: <1712942450.1137777041946.JavaMail.jira@ajax.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

     [ http://issues.apache.org/jira/browse/DDLUTILS-62?page=all ]

Appajee Papolu updated DDLUTILS-62:
-----------------------------------

    Description: 
- 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 '('&apos;some string&apos;')' 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.


  was:
- 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 '('0')' 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 to use near '0')' NULL

- I changed the col3 line to as follows and then the ddltodatabase works fine
    `col3` CHAR(1) DEFAULT '0' NULL

- I could not find info if there were any user configurable settings that can overcome this problem.


> CLONE -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
>         Type: Bug
>  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
>     Assignee: Thomas Dudziak

>
> - 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 '('&apos;some string&apos;')' 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