Mailing-List: contact ddlutils-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ddlutils-dev@db.apache.org
Message-ID: <19819202.1152772230202.JavaMail.jira@brutus>
Date: Thu, 13 Jul 2006 06:30:30 +0000 (GMT+00:00)
From: "Thomas Dudziak (JIRA)" <jira@apache.org>
To: ddlutils-dev@db.apache.org
Subject: [jira] Updated: (DDLUTILS-61) column DEFAULT - SQL error during
 create table  in ddlToDatabase( to MySQL)  using  files produced by
 databaseToDdl(from MSSQL)
In-Reply-To: <1512010482.1137776801969.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-61?page=all ]

Thomas Dudziak updated DDLUTILS-61:
-----------------------------------

    Fix Version: 1.0

> column DEFAULT - SQL error during create table  in ddlToDatabase( to MySQL)  using  files produced by databaseToDdl(from MSSQL)
> -------------------------------------------------------------------------------------------------------------------------------
>
>          Key: DDLUTILS-61
>          URL: http://issues.apache.org/jira/browse/DDLUTILS-61
>      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
>      Fix For: 1.0

>
> - 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.

-- 
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