[jira] Updated: (DDLUTILS-63) ddltoDatabase errors due to specific string values in table rows of data.xml -- ddltoDatabase(to MySQL) using files produced by databaseToDdl(from MSSQL)
[ http://issues.apache.org/jira/browse/DDLUTILS-63?page=all ] Thomas Dudziak updated DDLUTILS-63: --- Component: Core (No specific database) ddltoDatabase errors due to specific string values in table rows of data.xml -- ddltoDatabase(to MySQL) using files produced by databaseToDdl(from MSSQL) -- Key: DDLUTILS-63 URL: http://issues.apache.org/jira/browse/DDLUTILS-63 Project: DdlUtils Type: Bug Components: Core (No specific database) Environment: Win 2K SQL Server jtds MySQL 5.0 MySQL Connector/J Reporter: Appajee Papolu Assignee: Thomas Dudziak Fix For: 1.0 - Dumped out a MSSQL database using ddlutils ant task - Used the resulting files to create a database in MySQL - Getting errors while importing data that have embedded XML data in their row data, for example, as in: whatever-table col1=78 col2=name col2=Set-schema: User#1;$%$#10;Query: #2; '104' LIKE quot;$GID$;%quot; OR '104' LIKE quot;%;$GID$;%quot; OR '104' LIKE quot;% $GID$;%quot;#10;Entry-list: #10;window-position: 0518 0145 0395 0326#10;end#10;/ - Receiving error as follows: [ddlToDatabase] Jan 20, 2006 7:36:58 AM org.apache.commons.digester.Digester fatalError [ddlToDatabase] SEVERE: Parse Fatal Error at line 1705 column 107: Character reference #1 is an invalid XML character. [ddlToDatabase] org.xml.sax.SAXParseException: Character reference #1 is an invalid XML character. -- 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
[jira] Updated: (DDLUTILS-60) JDBC Type BIGINT in Firebird
[ http://issues.apache.org/jira/browse/DDLUTILS-60?page=all ] Thomas Dudziak updated DDLUTILS-60: --- Component: Core - Firebird Core - Interbase JDBC Type BIGINT in Firebird Key: DDLUTILS-60 URL: http://issues.apache.org/jira/browse/DDLUTILS-60 Project: DdlUtils Type: Bug Components: Core - Firebird, Core - Interbase Environment: SuSE Linux 10.0, Firebird 2.0 Beta1, JDK 1.5.0_06, JayBird 2.0.1, Reporter: Andre Berten Assignee: Thomas Dudziak The jdbc type BIGINT is converted to the database type DECIMAL(38,0). Firebird does support DECIMAL (and NUMERIC) with a maximum precision of 18. NUMERIC(18,0) or DECIMAL(18,0) should work fine as a conversion of BIGINT. The NUMERIC and DECIMAL types did not change since InterBase 6.0, so this should work for InterBase 6.0 too. Since Firebird 1.5 there is also the native BIGINT type. -- 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
[jira] Updated: (DDLUTILS-57) Replace DateConverter's and TimeConverter's use of deprecated constructors
[ http://issues.apache.org/jira/browse/DDLUTILS-57?page=all ] Thomas Dudziak updated DDLUTILS-57: --- Component: Core (No specific database) Replace DateConverter's and TimeConverter's use of deprecated constructors -- Key: DDLUTILS-57 URL: http://issues.apache.org/jira/browse/DDLUTILS-57 Project: DdlUtils Type: Improvement Components: Core (No specific database) Reporter: Ken Weiner Assignee: Thomas Dudziak Fix For: 1.0 Attachments: Converters-patch.txt Both DateConverter and TimeConverter use deprecated constructors of java.sql.Date and java.sql.Time respectively. This request is to replace the use of those constructors with a non-deprecated one. I am attaching a patch file that fixes both the DateConverter and TimeConverter to make use of the Calendar object to contruct the dates and times. This patch also adds a check to the convertToString methods to check the type of the object, throwing an exception if the object is not of the expected type. I also wrote some unit tests, DateConverterTest and TimeConverterTest to accompany these changes. Note: Before applying this patch, you could have called the convertFromString() methods with invalid text representations and the methods would have returned an unexpected date. Now with the use of Calendar, this won't happen since the Calendar instance has been set to not be lenient. See DateConverterTest.testConvertFromStringWithInvalidTextRep() and TimeConverter.testConvertFromStringWithInvalidTextRep(). These test methods do not pass with the current code, but do pass after applying this patch. -- 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
[jira] Updated: (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=all ]
Thomas Dudziak updated DDLUTILS-62:
---
Component: Core (No specific database)
Summary: column DEFAULT - SQL error during create table in
ddlToDatabase( to MySQL) using files produced by databaseToDdl(from MSSQL)
(was: CLONE -column DEFAULT - SQL error during create table in ddlToDatabase(
to MySQL) using files produced by databaseToDdl(from MSSQL))
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
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
Assignee: 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 '('apos;some stringapos;')' 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
[jira] Updated: (DDLUTILS-55) HsqlDb PlatformInfo should not use delimited identifiers
[ http://issues.apache.org/jira/browse/DDLUTILS-55?page=all ] Thomas Dudziak updated DDLUTILS-55: --- Component: Core - HSQLDB HsqlDb PlatformInfo should not use delimited identifiers Key: DDLUTILS-55 URL: http://issues.apache.org/jira/browse/DDLUTILS-55 Project: DdlUtils Type: Bug Components: Core - HSQLDB Reporter: Ken Weiner Assignee: Thomas Dudziak Attachments: HsqlDbPlatform-patch.txt Currently, when creating tables using HSQLDB, double quotes () are used surrounding the table names in each CREATE TABLE statement. For example, CREATE TABLE person ... As a result, it isn't possible to write SQL without putting double quotes around tables names. For example, this statement doesn't work: select * from person; But this one does: select * from person; If useDelimitedIdentifiers in PlatformInfo is set to false, then double quotes will not surround the table names in CREATE TABLE statements and then SQL statements will work as expected (without having to include the double quotes). I will attach a patch for this simple change. -- 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
[jira] Updated: (DDLUTILS-53) Incorrect syntax for modifying columns in Derby
[ http://issues.apache.org/jira/browse/DDLUTILS-53?page=all ] Thomas Dudziak updated DDLUTILS-53: --- Component: Core - Derby/Cloudscape/JavaDB Incorrect syntax for modifying columns in Derby --- Key: DDLUTILS-53 URL: http://issues.apache.org/jira/browse/DDLUTILS-53 Project: DdlUtils Type: Bug Components: Core - Derby/Cloudscape/JavaDB Reporter: Konstantinos Stathatos Assignee: Thomas Dudziak The SQL DdlUtils generates for modifying a column in Derby 10.1 seems incorrect. specifically it cxreates statements like ALTER TABLE coltype MODIFY COL_FLOAT DOUBLE PRECISION; According to the documentation the correct syntax would have to be ALTER TABLE coltype ALTER COL_FLOAT SET DATA TYPE DOUBLE PRECISION; -- 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
[jira] Updated: (DDLUTILS-52) MS-SQL errors with DEFAULTs in Alter Statements
[ http://issues.apache.org/jira/browse/DDLUTILS-52?page=all ] Thomas Dudziak updated DDLUTILS-52: --- Component: Core - SqlServer MS-SQL errors with DEFAULTs in Alter Statements - Key: DDLUTILS-52 URL: http://issues.apache.org/jira/browse/DDLUTILS-52 Project: DdlUtils Type: Bug Components: Core - SqlServer Environment: WinXP, Sql Server 2000, Java 1.4.2 Reporter: Colin Ritchie Assignee: Thomas Dudziak Fix For: 1.0 When the using the ant task writeSchemaToDatabase with SQL Server 2000 to a database already created, the columns with the default attribute report an error: [ddlToDatabase] SQL Command ALTER TABLE oci_switch [ddlToDatabase] ALTER COLUMN schd_status SMALLINT DEFAULT '0' NOT NULL failed with [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Incorrect syntax near the keyword 'DEFAULT'. Schema: table name=oci_switch column name=schd_status primaryKey=false required=true type=SMALLINT size=6 default=0 autoIncrement=false/ /table I believe in MS SQL, you cannot include a DEFAULT in an ALTER COLUMN. It is a seperate statement. -- 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
[jira] Updated: (DDLUTILS-51) BOOLEANINT for MS-SQL desires TINYINT, but uses SMALLINT
[ http://issues.apache.org/jira/browse/DDLUTILS-51?page=all ] Thomas Dudziak updated DDLUTILS-51: --- Component: Core - SqlServer BOOLEANINT for MS-SQL desires TINYINT, but uses SMALLINT Key: DDLUTILS-51 URL: http://issues.apache.org/jira/browse/DDLUTILS-51 Project: DdlUtils Type: Bug Components: Core - SqlServer Environment: WinXP Pro, SQL-Server 2000, java 1.4.2 Reporter: Colin Ritchie Assignee: Thomas Dudziak Priority: Minor Fix For: 1.0 Columns for MS-SQL with Type BOOLEANINT get the following error when using the ant task writeSchemaToDatabase: [ddlToDatabase] INFO: Altering column oci_schedules.schd_state [ddlToDatabase] INFO: desired = Column [name=schd_state; javaName=null; type=TINYINT; typeCode=-6; size=null; required=false; primaryKey=false; autoIncrement=false; defaultValue=null; precisionRadix=0; scale=0] [ddlToDatabase] INFO: current = Column [name=schd_state; javaName=null; type=SMALLINT; typeCode=5; size=5; required=false; primaryKey=false; autoIncrement=false; defaultValue=null; precisionRadix=5; scale=0] The following is a snippet of my configuration file: table name=oci_schedules column name=schd_state primaryKey=false required=false type=BOOLEANINT autoIncrement=false/ /table -- 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
[jira] Updated: (DDLUTILS-49) Problem Delimiter in Postgres (8.1)
[ http://issues.apache.org/jira/browse/DDLUTILS-49?page=all ]
Thomas Dudziak updated DDLUTILS-49:
---
Component: Core - PostgreSql
Problem Delimiter in Postgres (8.1)
---
Key: DDLUTILS-49
URL: http://issues.apache.org/jira/browse/DDLUTILS-49
Project: DdlUtils
Type: Bug
Components: Core - PostgreSql
Environment: DDL-Utils (svn-Version), Postgres 8.1, Jdbc-Driver of Postgres
8.1 Distribution.
Reporter: Robert Einsle
Assignee: Thomas Dudziak
while using DDL-Utils on Postgres 8.1 i found the following situation:
-- the xml ---
database name=test
table name=transactions
column name=trade_id primaryKey=true required=true type=INTEGER
size=4 autoIncrement=true /
column name=currency type=CHAR size=3 /
column name=product type=CHAR size=4 /
column name=description type=VARCHAR size=50 /
column name=exchange type=CHAR size=15 /
column name=quantity type=INTEGER size=4 /
column name=price type=NUMERIC size=15,4 /
column name=amount type=NUMERIC size=15,2 /
column name=symbol type=CHAR size=5 /
column name=securityid type=INTEGER size=4 /
index name=idx_transactions_product
index-column name=product/
/index
/table
/database
--- end xml ---
while creating an Table ddl-utils reports the creating of the Sequence. But
when creating the Table i recived the following Error:
--- cut ---
... failed with ERROR: column transactions_trade_id_seq does not exist
--- cut ---
--- generated SQL ---
CREATE TABLE transactions
(
trade_id INTEGER NOT NULL UNIQUE DEFAULT
nextval(transactions_trade_id_seq),
currency CHAR(3),
product CHAR(4),
description VARCHAR(50),
exchange CHAR(15),
quantity INTEGER,
price NUMERIC(15,4),
amount NUMERIC(15,2),
symbol CHAR(5),
securityid INTEGER
)
--- end SQL
On Documentation of Postgres i found this:
--- Psql Doc ---
CREATE SEQUENCE /tablename/_/colname/_seq;
CREATE TABLE /tablename/ (
/colname/ integer DEFAULT nextval('/tablename/_/colname/_seq') NOT NULL
);
--- end Doc ---
So i think the dopple Quotes in nextval should be single Quotes.
--
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
[jira] Updated: (DDLUTILS-45) createDatabase and alterDatabase should give access to the generated SQL.
[ http://issues.apache.org/jira/browse/DDLUTILS-45?page=all ] Thomas Dudziak updated DDLUTILS-45: --- Component: Core (No specific database) createDatabase and alterDatabase should give access to the generated SQL. - Key: DDLUTILS-45 URL: http://issues.apache.org/jira/browse/DDLUTILS-45 Project: DdlUtils Type: Improvement Components: Core (No specific database) Reporter: Thorbjørn Ravn Andersen Assignee: Thomas Dudziak Priority: Minor Attachments: sql-access.txt In a scenario where you work with XML-representations of databases, you do not necessarily want to first create the first schema in a database, and then alter to the second to see how it works. It would be quite suitable just to work on the models loaded from XML and then just generate the corresponding SQL without executing it. This would provide for debugging and documentation purposes. -- 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
[jira] Updated: (DDLUTILS-44) Column remarks are not stored in JdbcModelReader.getColumnsForTable
[ http://issues.apache.org/jira/browse/DDLUTILS-44?page=all ] Thomas Dudziak updated DDLUTILS-44: --- Component: Core (No specific database) Column remarks are not stored in JdbcModelReader.getColumnsForTable --- Key: DDLUTILS-44 URL: http://issues.apache.org/jira/browse/DDLUTILS-44 Project: DdlUtils Type: Bug Components: Core (No specific database) Reporter: Thorbjørn Ravn Andersen Assignee: Thomas Dudziak Priority: Minor Attachments: column-description.patch When reading in a Database from a physical database, the column comment is not stored in the internal object. The enclosed patch fixes this. -- 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
[jira] Updated: (DDLUTILS-43) jdbc model reader does not set the database name
[ http://issues.apache.org/jira/browse/DDLUTILS-43?page=all ] Thomas Dudziak updated DDLUTILS-43: --- Component: Core (No specific database) jdbc model reader does not set the database name Key: DDLUTILS-43 URL: http://issues.apache.org/jira/browse/DDLUTILS-43 Project: DdlUtils Type: Bug Components: Core (No specific database) Reporter: Thorbjørn Ravn Andersen Assignee: Thomas Dudziak Fix For: 1.0 On 11/7/05, Thorbjørn Ravn Andersen [EMAIL PROTECTED] wrote: I just noticed that the method described to read from a database, put together with the method to write to XML does not produce XML-files that can be read in again with the method to read from xml. I found that a database.setName(whatever) had to be called before writing to xml to remidy this. You're right, the jdbc model reader does not set the database name yet. Could you file an issue with JIRA ? Tom -- 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
[jira] Updated: (DDLUTILS-42) Index information is not read
[ http://issues.apache.org/jira/browse/DDLUTILS-42?page=all ] Thomas Dudziak updated DDLUTILS-42: --- Component: Core (No specific database) Index information is not read - Key: DDLUTILS-42 URL: http://issues.apache.org/jira/browse/DDLUTILS-42 Project: DdlUtils Type: Bug Components: Core (No specific database) Reporter: Thorbjørn Ravn Andersen Assignee: Thomas Dudziak Attachments: index.patch When loading table information from e.g. a database, the index information is not read. -- 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
[jira] Updated: (DDLUTILS-41) dropDatabase requires schema file for DdlToDatabaseTask
[ http://issues.apache.org/jira/browse/DDLUTILS-41?page=all ] Thomas Dudziak updated DDLUTILS-41: --- Component: Ant Tasks dropDatabase requires schema file for DdlToDatabaseTask --- Key: DDLUTILS-41 URL: http://issues.apache.org/jira/browse/DDLUTILS-41 Project: DdlUtils Type: Bug Components: Ant Tasks Reporter: Peter lynch Assignee: Thomas Dudziak Priority: Minor The Ant task documentation for dropDatabase states This sub task does not require schema files. Therefore the fileset subelement and the schemaFile attribute can be omitted. However if you don't specify a schema file you get this on stdout: [ddlToDatabase] No schemas read, so there is nothing to do. So either it truly doesn't and it is a bug that the check is performed, or it does and docs are wrong. -- 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
[jira] Updated: (DDLUTILS-38) Support for international date/time format in MSSQL
[ http://issues.apache.org/jira/browse/DDLUTILS-38?page=all ] Thomas Dudziak updated DDLUTILS-38: --- Component: Core - SqlServer Support for international date/time format in MSSQL --- Key: DDLUTILS-38 URL: http://issues.apache.org/jira/browse/DDLUTILS-38 Project: DdlUtils Type: Improvement Components: Core - SqlServer Reporter: JuanFran Adame Lorite Assignee: Thomas Dudziak Fix For: 1.1 Attachments: MSSqlBuilder.java, SqlBuilder.java MS SQL supports time, date, timestamp formats independents of locale in use. This patch set these formats as default (when no locale is set in SqlBuilder) to format date/time/timestamp values in SQL expressions. -- 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
[jira] Updated: (DDLUTILS-39) Creating Foreign Keys before creating the matching Tables
[ http://issues.apache.org/jira/browse/DDLUTILS-39?page=all ] Thomas Dudziak updated DDLUTILS-39: --- Component: Core - PostgreSql Creating Foreign Keys before creating the matching Tables - Key: DDLUTILS-39 URL: http://issues.apache.org/jira/browse/DDLUTILS-39 Project: DdlUtils Type: Bug Components: Core - PostgreSql Environment: Windows 2000, XP, Linux, Eclipse, PostgreSQL, hsqldb, MySQL Reporter: Robert Einsle Assignee: Thomas Dudziak Priority: Minor Fix For: 1.0 Attachments: lakon-db-neu.xml, lakon-db.xml While testing on an Postgres-Database, we have the Problem DDL-Utils works thrait throu the xml-Inputfile, and alters the Database. But we have an definition of an foreign key insertet in an table above the creation-rule of the table itself. So, DDL-Utils first tries to alter the Database, inserting the Foreign-key, fails, then creates the table. So, we have 2 choices, sorting the xml-inputfile for the foreign keys, or DDL-Utils let to create foreign keys after creating the needed Tables. For my choices i would prefer the second solution. Can i do anything other? -- 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
[jira] Updated: (DDLUTILS-40) Numeric formatting in MS SQL Server
[ http://issues.apache.org/jira/browse/DDLUTILS-40?page=all ] Thomas Dudziak updated DDLUTILS-40: --- Component: Core - SqlServer Numeric formatting in MS SQL Server --- Key: DDLUTILS-40 URL: http://issues.apache.org/jira/browse/DDLUTILS-40 Project: DdlUtils Type: Bug Components: Core - SqlServer Reporter: JuanFran Adame Lorite Assignee: Thomas Dudziak Priority: Minor Fix For: 1.0 Attachments: MSSqlBuilder.java Numeric values does not have to be surrounded by quotes in SQL commands, doing so can generate errors when MS SQL Server parses a scientific format number (with quotes surrounding) to DECIMAL o NUMERIC column. -- 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
[jira] Updated: (DDLUTILS-37) org.apache.ddlutils.model.Database implements Serializable but it's not
[ http://issues.apache.org/jira/browse/DDLUTILS-37?page=all ] Thomas Dudziak updated DDLUTILS-37: --- Component: Core (No specific database) org.apache.ddlutils.model.Database implements Serializable but it's not --- Key: DDLUTILS-37 URL: http://issues.apache.org/jira/browse/DDLUTILS-37 Project: DdlUtils Type: Bug Components: Core (No specific database) Reporter: JuanFran Adame Lorite Assignee: Thomas Dudziak Attachments: Database.java Although org.apache.ddlutils.model.Database implements Serializable interface it 's not because DynaClassCache class is not serializable and Database contains it. -- 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
[jira] Updated: (DDLUTILS-36) Getting tables from connection metadata has not homogeneous behaviour depending on products
[ http://issues.apache.org/jira/browse/DDLUTILS-36?page=all ] Thomas Dudziak updated DDLUTILS-36: --- Component: Core (No specific database) Getting tables from connection metadata has not homogeneous behaviour depending on products --- Key: DDLUTILS-36 URL: http://issues.apache.org/jira/browse/DDLUTILS-36 Project: DdlUtils Type: Improvement Components: Core (No specific database) Reporter: JuanFran Adame Lorite Assignee: Thomas Dudziak When getting tables metadata from database metadata in getTable method in org.apache.ddlutils.io.JdbcModelReader, the filters used do not work as a homogeneous way for all the products. In MS SQL Server, filtering with % in catalag does not return any table, null must be used indeed. Other users have reported similar problems with other solutions in MySQL. May this functionality be implemented in a product dependet class as SqlBuilder is? -- 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
[jira] Updated: (DDLUTILS-34) Credentials needed when using a DataSource
[ http://issues.apache.org/jira/browse/DDLUTILS-34?page=all ] Thomas Dudziak updated DDLUTILS-34: --- Component: Core (No specific database) Credentials needed when using a DataSource -- Key: DDLUTILS-34 URL: http://issues.apache.org/jira/browse/DDLUTILS-34 Project: DdlUtils Type: Bug Components: Core (No specific database) Environment: J2EE platforms with DataSource deployments Reporter: JuanFran Adame Lorite Assignee: Thomas Dudziak Priority: Minor Attachments: PlatformFactory.java, PlatformUtils.java When deployment of a DataSource in J2EE platforms when there is not default credentials (authentication user) for every connection for this DataSource, the method DataSource.getConnection(user,pass) must be used, so every connection is independently authenticated. DdlUtils may support these situations for PlatformFactory.createNewPlatformInstance. -- 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
[jira] Updated: (DDLUTILS-32) I want to be able to specify the table type/engine when i create tables in mysql.
[ http://issues.apache.org/jira/browse/DDLUTILS-32?page=all ] Thomas Dudziak updated DDLUTILS-32: --- Component: Core - MySql I want to be able to specify the table type/engine when i create tables in mysql. - Key: DDLUTILS-32 URL: http://issues.apache.org/jira/browse/DDLUTILS-32 Project: DdlUtils Type: New Feature Components: Core - MySql Reporter: Christoffer Hammarström Assignee: Thomas Dudziak Attachments: DDLUTILS-32.patch In MySQL, a table type or engine can be specified after the create table statement, like so: CREATE TABLE table ( column INTEGER ) ENGINE=InnoDB TYPE is a synonym for ENGINE. http://dev.mysql.com/doc/refman/4.1/en/storage-engines.html says ENGINE is the preferred term, but cannot be used before MySQL 4.0.18. TYPE is available beginning with MySQL 3.23.0, the first version of MySQL for which multiple storage engines were available. -- 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
[jira] Updated: (DDLUTILS-31) Generated XML data dump is invalid
[ http://issues.apache.org/jira/browse/DDLUTILS-31?page=all ] Thomas Dudziak updated DDLUTILS-31: --- Component: Core (No specific database) Generated XML data dump is invalid -- Key: DDLUTILS-31 URL: http://issues.apache.org/jira/browse/DDLUTILS-31 Project: DdlUtils Type: Bug Components: Core (No specific database) Environment: any Reporter: Alexandre Borgoltz Assignee: Thomas Dudziak in DataWriter, data is not xml-escaped before it is written to the xml file. This makes invalid files. Typically, a '' character like in HeavenHell should be escaped to heavenamp;Hell. idem for , , -- 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
[jira] Updated: (DDLUTILS-30) Encoding not supported
[ http://issues.apache.org/jira/browse/DDLUTILS-30?page=all ] Thomas Dudziak updated DDLUTILS-30: --- Component: Core (No specific database) Encoding not supported -- Key: DDLUTILS-30 URL: http://issues.apache.org/jira/browse/DDLUTILS-30 Project: DdlUtils Type: Bug Components: Core (No specific database) Environment: any Reporter: Alexandre Borgoltz Assignee: Thomas Dudziak The DataWriter's output is hardcoded to be UTF-8: ?xml version=\1.0\ encoding=\UTF-8\? with no way to select another encoding. The data that is stored in my DB is ISO-8859-1 and thus the generated data XML dump is invalid. -- 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
[jira] Updated: (DDLUTILS-29) Stream is already closed with Oracle
[ http://issues.apache.org/jira/browse/DDLUTILS-29?page=all ] Thomas Dudziak updated DDLUTILS-29: --- Component: Core - Oracle Stream is already closed with Oracle -- Key: DDLUTILS-29 URL: http://issues.apache.org/jira/browse/DDLUTILS-29 Project: DdlUtils Type: Bug Components: Core - Oracle Environment: Using oracle10g jdbc client driver with oracle 8i server Reporter: Alexandre Borgoltz Assignee: Thomas Dudziak Attachments: oracle_COLUMN_DEF_bug.patch I get a SQLException stating that the stream is already closed. It occurs in at org.apache.ddlutils.io.JdbcModelReader.getValueAsString for the COLUMN_DEF column. Here is the stack trace - as you can see, I am using the ant task, with the sample xml provided on DdlUtils' site. java.sql.SQLException: Le flux de données est déjà fermé at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162) at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227) at oracle.jdbc.driver.LongAccessor.getBytes(LongAccessor.java:166) at oracle.jdbc.driver.LongAccessor.getString(LongAccessor.java:207) at oracle.jdbc.driver.T4CLongAccessor.getString(T4CLongAccessor.java:390) at oracle.jdbc.driver.OracleResultSetImpl.getString(OracleResultSetImpl.java:355) at oracle.jdbc.driver.OracleResultSet.getString(OracleResultSet.java:1559) at org.apache.ddlutils.io.JdbcModelReader.getValueAsString(JdbcModelReader.java:494) at org.apache.ddlutils.io.JdbcModelReader.getColumnsForTable(JdbcModelReader.java:277) at org.apache.ddlutils.io.JdbcModelReader.getTables(JdbcModelReader.java:205) at org.apache.ddlutils.io.JdbcModelReader.getDatabase(JdbcModelReader.java:140) at org.apache.ddlutils.task.DatabaseToDdlTask.readSchema(DatabaseToDdlTask.java:194) at org.apache.ddlutils.task.DatabaseToDdlTask.execute(DatabaseToDdlTask.java:214) I have tested it with 8i, 9i and 10g versions of the client oracle driver - same result. It highly looks like this is a bug in oracle's drivers management of Long fields. My tests proved that resultset.getString(COLUMN_DEF) : +can't be called twice (if .next() is not called obviously) +always fails for primary fields with 9i- drivers +fails if called after e.g. .getString(IS_NULLABLE) with 10g drivers +works OK if called first *with 10g drivers* So what I did is modify JdbcModelReader.getColumnsForTable(DatabaseMetaData, String) and move the call of getValueAsString(..., COLUMN_DEF, ...) to be the first one called. This works perfectly on my platform now. I'll attach the corresponding patch -- 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
[jira] Updated: (DDLUTILS-27) Capture and maintenance of column level comment fields
[ http://issues.apache.org/jira/browse/DDLUTILS-27?page=all ] Thomas Dudziak updated DDLUTILS-27: --- Component: Core (No specific database) Capture and maintenance of column level comment fields -- Key: DDLUTILS-27 URL: http://issues.apache.org/jira/browse/DDLUTILS-27 Project: DdlUtils Type: New Feature Components: Core (No specific database) Environment: SQL Server Reporter: Peter Millington Assignee: Thomas Dudziak Priority: Minor Fix For: 1.1 The database meta-schema (UML) includes a table-level remark attribute, but not ones for other entities - such as columns, keys etc. Can this be added with an option-flag to enable/disable copying of this field to a target schema or database? -- 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
[jira] Updated: (DDLUTILS-26) MySQL drop foreign key
[ http://issues.apache.org/jira/browse/DDLUTILS-26?page=all ]
Thomas Dudziak updated DDLUTILS-26:
---
Component: Core - MySql
MySQL drop foreign key
--
Key: DDLUTILS-26
URL: http://issues.apache.org/jira/browse/DDLUTILS-26
Project: DdlUtils
Type: Bug
Components: Core - MySql
Reporter: Xavier TROUSSICOT
Assignee: Thomas Dudziak
The writeExternalForeignKeyDropStmt method needs to be overriden in
MySqlBuilder class :
protected void writeExternalForeignKeyDropStmt(Table table, ForeignKey
foreignKey) throws IOException
{
writeTableAlterStmt(table);
print(DROP FOREIGN KEY );
printIdentifier(foreignKey.getName() == null ?
getConstraintName(null, table, FK, getForeignKeyName(foreignKey)) :
foreignKey.getName());
printEndOfStatement();
}
--
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
[jira] Updated: (DDLUTILS-24) Insert / update collection of Dynabean
[ http://issues.apache.org/jira/browse/DDLUTILS-24?page=all ] Thomas Dudziak updated DDLUTILS-24: --- Component: Core (No specific database) Insert / update collection of Dynabean -- Key: DDLUTILS-24 URL: http://issues.apache.org/jira/browse/DDLUTILS-24 Project: DdlUtils Type: Improvement Components: Core (No specific database) Environment: All Reporter: Xavier TROUSSICOT Assignee: Thomas Dudziak The insert method in the PlatformImplBase class does not accept Collection or Iterator of Dynabean . It could be usefull as it is for the DataWriter.write method. This improvement should commit by packet. It could be done through DataToDatabaseSink class but the commit is done after each bean. Whatis your opinion about it ? -- 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
[jira] Updated: (DDLUTILS-23) Method write(Iterator beans) in DataWriter class doesn't work
[ http://issues.apache.org/jira/browse/DDLUTILS-23?page=all ]
Thomas Dudziak updated DDLUTILS-23:
---
Component: Core (No specific database)
Method write(Iterator beans) in DataWriter class doesn't work
-
Key: DDLUTILS-23
URL: http://issues.apache.org/jira/browse/DDLUTILS-23
Project: DdlUtils
Type: Bug
Components: Core (No specific database)
Environment: All
Reporter: Xavier TROUSSICOT
Assignee: Thomas Dudziak
The next() method is not called so the cast doesn't work.
Here is the correction :
public void write(Iterator beans)
{
while (beans.hasNext())
{
write((SqlDynaBean)beans.next());
}
}
--
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
[jira] Updated: (DDLUTILS-22) DB2 type mapping for BOOLEAN should be SMALLINT?
[ http://issues.apache.org/jira/browse/DDLUTILS-22?page=all ] Thomas Dudziak updated DDLUTILS-22: --- Component: Core - DB2 DB2 type mapping for BOOLEAN should be SMALLINT? Key: DDLUTILS-22 URL: http://issues.apache.org/jira/browse/DDLUTILS-22 Project: DdlUtils Type: Bug Components: Core - DB2 Reporter: Richard Bounds Assignee: Thomas Dudziak The mapping in Db2Platform for BOOLEAN is currently CHAR FOR BIT DATA. According to these docs: http://publib.boulder.ibm.com/infocenter/db2help/topic/com.ibm.db2.udb.doc/ad/rjvjdata.htm#jvregou it looks like it should be 'SMALLINT' ? -- 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
[jira] Updated: (DDLUTILS-21) Sql Server drop statements fail without delimited identifiers
[ http://issues.apache.org/jira/browse/DDLUTILS-21?page=all ] Thomas Dudziak updated DDLUTILS-21: --- Component: Core - SqlServer Sql Server drop statements fail without delimited identifiers - Key: DDLUTILS-21 URL: http://issues.apache.org/jira/browse/DDLUTILS-21 Project: DdlUtils Type: Bug Components: Core - SqlServer Reporter: Richard Bounds Assignee: Thomas Dudziak Attachments: patch.txt The drop statements that are generated for sql server are prefixed by: IF EXISTS (SELECT 1 FROM sysobjects WHERE type = 'U' AND name = 'tablename') Without a delimeter being specified the statement changes to: IF EXISTS (SELECT 1 FROM sysobjects WHERE type = 'U' AND name = tablename) ...which fails (note the lack of quotes around tablename). -- 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
[jira] Updated: (DDLUTILS-20) Oracle FLOAT and DOUBLE type mappings have zero scale
[ http://issues.apache.org/jira/browse/DDLUTILS-20?page=all ] Thomas Dudziak updated DDLUTILS-20: --- Component: Core - Oracle Oracle FLOAT and DOUBLE type mappings have zero scale - Key: DDLUTILS-20 URL: http://issues.apache.org/jira/browse/DDLUTILS-20 Project: DdlUtils Type: Bug Components: Core - Oracle Reporter: Richard Bounds Assignee: Thomas Dudziak Fix For: 1.0 Attachments: metadata.xml In Oracle8Platform, the types FLOAT and DOUBLE are mapped to NUMBER(38). According to Oracle's docs, this type has zero scale. It looks like floating point numbers should be specified either as just NUMBER or FLOAT(n). See: http://oraclelon1.oracle.com/docs/cd/B19306_01/server.102/b14200/sql_elements001.htm#g196646 -- 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
[jira] Updated: (DDLUTILS-19) index tag and unique tag exists in dtd but DatabaseIO().write generate XML without index and unique elements
[ http://issues.apache.org/jira/browse/DDLUTILS-19?page=all ] Thomas Dudziak updated DDLUTILS-19: --- Component: Core (No specific database) index tag and unique tag exists in dtd but DatabaseIO().write generate XML without index and unique elements Key: DDLUTILS-19 URL: http://issues.apache.org/jira/browse/DDLUTILS-19 Project: DdlUtils Type: Bug Components: Core (No specific database) Environment: Linux Fedora 4 jdk1.5.0_04 Reporter: Andre Charles Legendre Assignee: Thomas Dudziak Fix For: 1.0 index tag and unique tag exists in both dtd but I found no index element nor unique element created when I have generated XML from our database using DatabaseIO().write For example a postgres table created by : CREATE TABLE MFG_BatchType ( Idnumeric(10,0) unique not null, AD_Client_ID numeric(10,0) not null, AD_Org_ID numeric(10,0) not null, IsActive varchar(1) not null default 'Y', Created timestamp not null default CURRENT_TIMESTAMP, CreatedBy numeric(10,0) not null, Updated timestamp not null default CURRENT_TIMESTAMP, UpdatedBy numeric(10,0) not null, Name varchar(200)not null, No_versionvarchar(32) not null, Description varchar(2000) not null, Cycle_Timenumeric(10,0) not null, Cycle_Qty float8 not null, primary key(Id) ); CREATE INDEX MFG_BatchTypeNDX1 ON MFG_BatchType(Id); -- -- COMMENT ON COLUMN MFG_BatchType.Description is 'Cycle, one shot or when completed'; COMMENT ON COLUMN MFG_BatchType.Cycle_Time is 'if batch type is cycle'; COMMENT ON COLUMN MFG_BatchType.Cycle_Qty is 'Number of work orders to introduce when WIP minimum is reached'; Give this XML : table name=mfg_batchtype column name=id primaryKey=false required=true type=NUMERIC size=10 autoIncrement=false/ column name=ad_client_id primaryKey=false required=true type=NUMERIC size=10 autoIncrement=false/ column name=ad_org_id primaryKey=false required=true type=NUMERIC size=10 autoIncrement=false/ column name=isactive primaryKey=false required=true type=VARCHAR size=1 default=apos;Yapos;::character varying autoIncrement=false/ column name=created primaryKey=false required=true type=TIMESTAMP size=8 default=(apos;nowapos;::text)::timestamp(6) with time zone autoIncrement=false/ column name=createdby primaryKey=false required=true type=NUMERIC size=10 autoIncrement=false/ column name=updated primaryKey=false required=true type=TIMESTAMP size=8 default=(apos;nowapos;::text)::timestamp(6) with time zone autoIncrement=false/ column name=updatedby primaryKey=false required=true type=NUMERIC size=10 autoIncrement=false/ column name=name primaryKey=false required=true type=VARCHAR size=200 autoIncrement=false/ column name=no_version primaryKey=false required=true type=VARCHAR size=32 autoIncrement=false/ column name=description primaryKey=false required=true type=VARCHAR size=2000 autoIncrement=false/ column name=cycle_time primaryKey=false required=true type=NUMERIC size=10 autoIncrement=false/ column name=cycle_qty primaryKey=false required=true type=DOUBLE size=8 autoIncrement=false/ /table As you can see index and comment disapear for comment, it is not an issue but for index yes. -- 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
[jira] Updated: (DDLUTILS-17) MS SQL Server DATETIME column
[ http://issues.apache.org/jira/browse/DDLUTILS-17?page=all ] Thomas Dudziak updated DDLUTILS-17: --- Component: Core - SqlServer MS SQL Server DATETIME column - Key: DDLUTILS-17 URL: http://issues.apache.org/jira/browse/DDLUTILS-17 Project: DdlUtils Type: Bug Components: Core - SqlServer Environment: MS SQL Server 2000 Reporter: dan meany Assignee: Thomas Dudziak Priority: Minor I had trouble creating a MS SQL Server DATETIME column with DdlUtils (TypeMap.java does not have a DATETIME?). MS SQL Server 2000 does not have a DATE or TIME column type. They have a DATETIME and a TIMESTAMP. There can only be one TIMESTAMP column per table, but multiple DATETIMES are ok. For reference the MS SQL types I have are: bigint binary bit char datetime decimal float image int money nchar ntext numeric nvarchar real smalldatetime smallint smallmoney sql_variant text timestamp tinyint uniqueidentifier varbinary varchar -- 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
[jira] Updated: (DDLUTILS-14) Sybase autoincrement column
[ http://issues.apache.org/jira/browse/DDLUTILS-14?page=all ] Thomas Dudziak updated DDLUTILS-14: --- Component: Core - Sybase Sybase autoincrement column --- Key: DDLUTILS-14 URL: http://issues.apache.org/jira/browse/DDLUTILS-14 Project: DdlUtils Type: Bug Components: Core - Sybase Environment: Sybase Reporter: dan meany Assignee: Thomas Dudziak Fix For: 1.0 Reading a Sybase ASA schema with an autoincrement column produces default=autoincrement autoIncrement=false instead of autoIncrement=true -- 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
[jira] Updated: (DDLUTILS-18) DB2 autoincrement
[ http://issues.apache.org/jira/browse/DDLUTILS-18?page=all ] Thomas Dudziak updated DDLUTILS-18: --- Component: Core - DB2 DB2 autoincrement - Key: DDLUTILS-18 URL: http://issues.apache.org/jira/browse/DDLUTILS-18 Project: DdlUtils Type: Bug Components: Core - DB2 Environment: DB2 version 8 Reporter: dan meany Assignee: Thomas Dudziak Fix For: 1.0 Reading table schema for an autoincrement column in DB2 v.8 produces: column name=SEQ_NO primaryKey=true required=true type=INTEGER size=10 default=IDENTITY GENERATED BY DEFAULT autoIncrement=false/ Should be autoIncrement=true -- 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
[jira] Updated: (DDLUTILS-16) Support for options when creating databases
[ http://issues.apache.org/jira/browse/DDLUTILS-16?page=all ] Thomas Dudziak updated DDLUTILS-16: --- Component: Core (No specific database) Support for options when creating databases --- Key: DDLUTILS-16 URL: http://issues.apache.org/jira/browse/DDLUTILS-16 Project: DdlUtils Type: New Feature Components: Core (No specific database) Reporter: Thomas Dudziak Assignee: Thomas Dudziak Eg. for specifying the locale such that for PostgreSQL a CREATE DATABASE DbWithLocale WITH ENCODING = 'LATIN1' is issued if the option 'encoding' is set to 'LATIN1' -- 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
[jira] Updated: (DDLUTILS-12) cache metadata from connection
[ http://issues.apache.org/jira/browse/DDLUTILS-12?page=all ] Thomas Dudziak updated DDLUTILS-12: --- Component: Core (No specific database) cache metadata from connection -- Key: DDLUTILS-12 URL: http://issues.apache.org/jira/browse/DDLUTILS-12 Project: DdlUtils Type: Improvement Components: Core (No specific database) Reporter: dan meany Assignee: Thomas Dudziak Priority: Minor connection.getMetaData() is called many times in org.apache.ddlutils.io.JdbcModelReader. Consider caching the metadata object along with the connection. -- 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
[jira] Updated: (DDLUTILS-9) shouldGeneratePrimaryKeys(List) changed to shouldGeneratePrimaryKeys(Column[]) in SqlBuilder, but not in its subclasses.
[ http://issues.apache.org/jira/browse/DDLUTILS-9?page=all ] Thomas Dudziak updated DDLUTILS-9: -- Component: Core (No specific database) shouldGeneratePrimaryKeys(List) changed to shouldGeneratePrimaryKeys(Column[]) in SqlBuilder, but not in its subclasses. Key: DDLUTILS-9 URL: http://issues.apache.org/jira/browse/DDLUTILS-9 Project: DdlUtils Type: Bug Components: Core (No specific database) Reporter: Christoffer Hammarström Assignee: Thomas Dudziak Attachments: shouldGeneratePrimaryKeys.patch This means that this method is not called in the subclasses when appropriate. -- 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
[jira] Updated: (DDLUTILS-8) MsSqlBuilder can't alter a table to make a column autoincremented (identity)
[ http://issues.apache.org/jira/browse/DDLUTILS-8?page=all ]
Thomas Dudziak updated DDLUTILS-8:
--
Component: Core - SqlServer
MsSqlBuilder can't alter a table to make a column autoincremented (identity)
Key: DDLUTILS-8
URL: http://issues.apache.org/jira/browse/DDLUTILS-8
Project: DdlUtils
Type: Bug
Components: Core - SqlServer
Reporter: Christoffer Hammarström
Assignee: Thomas Dudziak
Fix For: 1.0
Attachments: DDLUTILS-8-1st-draft.patch, DDLUTILS-8-2nd-draft.patch
A column in an existing table can't be made autoincremented using ALTER TABLE.
I want to add this capability to MsSqlBuilder, but i'm not sure whether to
copy the approach of Microsoft Enterprise Manager, or if there is some better
way, and i would like some direction or input.
I've started by extracting methods alterTable() and alterColumns() from
alterDatabase() in SqlBuilder, and i'm overriding alterColumns() in
MsSqlBuilder with a check for autoincremented columns in the desiredTable but
not in the currentTable.
The approach used when scripting this change from Microsoft Enterprise
Manager is to:
1. Drop table constraints
2. Create a new replacement table with the name prefixed by 'Tmp_'
3. SET IDENTITY_INSERT Tmp_table ON
4. Copy the data from the table to the Tmp_table
5. Set IDENTITY_INSERT Tmp_table OFF
6. DROP TABLE table
7. EXECUTE sp_rename N'dbo.Tmp_table', N'table', 'OBJECT'
8. Readd table constraints
An example follows:
BEGIN TRANSACTION
SET QUOTED_IDENTIFIER ON
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
SET ARITHABORT ON
SET NUMERIC_ROUNDABORT OFF
SET CONCAT_NULL_YIELDS_NULL ON
SET ANSI_NULLS ON
SET ANSI_PADDING ON
SET ANSI_WARNINGS ON
COMMIT
BEGIN TRANSACTION
ALTER TABLE dbo.phones
DROP CONSTRAINT FK_phones_users
GO
COMMIT
BEGIN TRANSACTION
ALTER TABLE dbo.phones
DROP CONSTRAINT DF_phones_phonetype_id
GO
CREATE TABLE dbo.Tmp_phones
(
phone_id int NOT NULL IDENTITY (1, 1),
number varchar(25) NOT NULL,
user_id int NOT NULL,
phonetype_id int NOT NULL
) ON [PRIMARY]
GO
ALTER TABLE dbo.Tmp_phones ADD CONSTRAINT
DF_phones_phonetype_id DEFAULT (0) FOR phonetype_id
GO
SET IDENTITY_INSERT dbo.Tmp_phones ON
GO
IF EXISTS(SELECT * FROM dbo.phones)
EXEC('INSERT INTO dbo.Tmp_phones (phone_id, number, user_id, phonetype_id)
SELECT phone_id, number, user_id, phonetype_id FROM dbo.phones TABLOCKX')
GO
SET IDENTITY_INSERT dbo.Tmp_phones OFF
GO
DROP TABLE dbo.phones
GO
EXECUTE sp_rename N'dbo.Tmp_phones', N'phones', 'OBJECT'
GO
ALTER TABLE dbo.phones ADD CONSTRAINT
PK_phones PRIMARY KEY NONCLUSTERED
(
phone_id,
user_id
) ON [PRIMARY]
GO
ALTER TABLE dbo.phones WITH NOCHECK ADD CONSTRAINT
FK_phones_users FOREIGN KEY
(
user_id
) REFERENCES dbo.users
(
user_id
)
GO
COMMIT
--
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
[jira] Updated: (DDLUTILS-6) Exception in Table.getPrimaryKeyColumns(), .getNonUniqueIndices(), .getUniqueIndices() because PredicatedList used where CollectionUtils.select() was intended.
[ http://issues.apache.org/jira/browse/DDLUTILS-6?page=all ] Thomas Dudziak updated DDLUTILS-6: -- Component: Core (No specific database) Exception in Table.getPrimaryKeyColumns(), .getNonUniqueIndices(), .getUniqueIndices() because PredicatedList used where CollectionUtils.select() was intended. --- Key: DDLUTILS-6 URL: http://issues.apache.org/jira/browse/DDLUTILS-6 Project: DdlUtils Type: Bug Components: Core (No specific database) Reporter: Christoffer Hammarström Assignee: Thomas Dudziak Attachments: table.patch java.lang.IllegalArgumentException: Cannot add Object '[EMAIL PROTECTED];type=null]' - Predicate rejected it at org.apache.commons.collections.collection.PredicatedCollection.validate(PredicatedCollection.java:100) at org.apache.commons.collections.collection.PredicatedCollection.init(PredicatedCollection.java:85) at org.apache.commons.collections.list.PredicatedList.init(PredicatedList.java:79) at org.apache.commons.collections.list.PredicatedList.decorate(PredicatedList.java:63) at org.apache.ddlutils.model.Table.getPrimaryKeyColumns(Table.java:571) -- 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
[jira] Updated: (DDLUTILS-5) I'm unable to specify that i don't want any sql drops generated with WriteSchemaSqlToFileCommand
[ http://issues.apache.org/jira/browse/DDLUTILS-5?page=all ] Thomas Dudziak updated DDLUTILS-5: -- Component: Ant Tasks I'm unable to specify that i don't want any sql drops generated with WriteSchemaSqlToFileCommand Key: DDLUTILS-5 URL: http://issues.apache.org/jira/browse/DDLUTILS-5 Project: DdlUtils Type: Improvement Components: Ant Tasks Reporter: Christoffer Hammarström Assignee: Thomas Dudziak Priority: Trivial Attachments: dodrops.patch When generating SQL DDL using Ant, i don't want any drop statements, but i'm unable to say so. -- 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
[jira] Updated: (DDLUTILS-1) Added several native type mappings for Hsqldb
[ http://issues.apache.org/jira/browse/DDLUTILS-1?page=all ] Thomas Dudziak updated DDLUTILS-1: -- Component: Core - HSQLDB Added several native type mappings for Hsqldb - Key: DDLUTILS-1 URL: http://issues.apache.org/jira/browse/DDLUTILS-1 Project: DdlUtils Type: Improvement Components: Core - HSQLDB Reporter: David Carlson Assignee: Thomas Dudziak Priority: Minor Attachments: ddlutils_hsqldb_typemapping.patch Added native type mapping to support various JDBC types in HSQLDB. Added cooresponding test for HSQLDB (similar to the postgres test). -- 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
[jira] Updated: (DDLUTILS-61) 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-61?page=all ]
Thomas Dudziak updated DDLUTILS-61:
---
Component: Core - SqlServer
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
Components: Core - SqlServer
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
[jira] Updated: (DDLUTILS-59) Maven 2 Plugin for DdlToDatabase and DatabaseToDdl
[ http://issues.apache.org/jira/browse/DDLUTILS-59?page=all ] Thomas Dudziak updated DDLUTILS-59: --- Component: Build Maven 2 Plugin for DdlToDatabase and DatabaseToDdl -- Key: DDLUTILS-59 URL: http://issues.apache.org/jira/browse/DDLUTILS-59 Project: DdlUtils Type: New Feature Components: Build Reporter: Ken Weiner Assignee: Martin van den Bemt Attachments: maven-ddlutils-plugin.zip This is a request for a Maven 2 plugin to offer the same functionality is available via the Ant tasks DdlToDatabase and DatabaseToDdl. -- 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
[jira] Created: (DDLUTILS-116) Fully support multiple schemas
Fully support multiple schemas -- Key: DDLUTILS-116 URL: http://issues.apache.org/jira/browse/DDLUTILS-116 Project: DdlUtils Type: Improvement Components: Core (No specific database) Reporter: Thomas Dudziak Assigned to: Thomas Dudziak Priority: Critical Fix For: 1.1 Multiple schemas in one database should be supported fully in both ways: model (XML with new 'schema' elements/attributes) - database that supports multiple schemas -- 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
[jira] Updated: (DDLUTILS-117) Use an XML schema instead of a DTD
[ http://issues.apache.org/jira/browse/DDLUTILS-117?page=all ] Thomas Dudziak updated DDLUTILS-117: Component: Core (No specific database) Priority: Critical (was: Major) Use an XML schema instead of a DTD -- Key: DDLUTILS-117 URL: http://issues.apache.org/jira/browse/DDLUTILS-117 Project: DdlUtils Type: Improvement Components: Core (No specific database) Reporter: Thomas Dudziak Assignee: Thomas Dudziak Priority: Critical Fix For: 1.1 In order to better support user-defined elements in the XML model files (which DdlUtils then can ignore), and to allow for separation of the elements that are interesting to DdlUtils vs. those that are intended to be used by Torque only, an XML schema for the model files is required. A first version is already in Subversion at: http://svn.apache.org/viewvc/db/ddlutils/trunk/src/schema/database.xsd?view=markup -- 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
[jira] Resolved: (DDLUTILS-47) The PK constraint should be generated even if a column is an identity column (except for Hsqldb)
[ http://issues.apache.org/jira/browse/DDLUTILS-47?page=all ] Thomas Dudziak resolved DDLUTILS-47. Resolution: Fixed As tested via TestConstraints#testPrimaryKeyAutoIncrementColumn() The PK constraint should be generated even if a column is an identity column (except for Hsqldb) Key: DDLUTILS-47 URL: http://issues.apache.org/jira/browse/DDLUTILS-47 Project: DdlUtils Issue Type: Bug Components: Core (No specific database) Environment: Tested on Hsql and Derby Reporter: Juliano Julio Assigned To: Thomas Dudziak Priority: Blocker Fix For: 1.0 I took the liberty to change the description a bit to make the bug clearer -- 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
[jira] Resolved: (DDLUTILS-52) MS-SQL errors with DEFAULTs in Alter Statements
[ http://issues.apache.org/jira/browse/DDLUTILS-52?page=all ] Thomas Dudziak resolved DDLUTILS-52. Resolution: Fixed Yes, the default has to be added manually via ALTER TABLE ADD CONSTRAINT (and a previous default must be dropped before) MS-SQL errors with DEFAULTs in Alter Statements - Key: DDLUTILS-52 URL: http://issues.apache.org/jira/browse/DDLUTILS-52 Project: DdlUtils Issue Type: Bug Components: Core - SqlServer Environment: WinXP, Sql Server 2000, Java 1.4.2 Reporter: Colin Ritchie Assigned To: Thomas Dudziak Fix For: 1.0 When the using the ant task writeSchemaToDatabase with SQL Server 2000 to a database already created, the columns with the default attribute report an error: [ddlToDatabase] SQL Command ALTER TABLE oci_switch [ddlToDatabase] ALTER COLUMN schd_status SMALLINT DEFAULT '0' NOT NULL failed with [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]Incorrect syntax near the keyword 'DEFAULT'. Schema: table name=oci_switch column name=schd_status primaryKey=false required=true type=SMALLINT size=6 default=0 autoIncrement=false/ /table I believe in MS SQL, you cannot include a DEFAULT in an ALTER COLUMN. It is a seperate statement. -- 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
[jira] Resolved: (DDLUTILS-8) MsSqlBuilder can't alter a table to make a column autoincremented (identity)
[ http://issues.apache.org/jira/browse/DDLUTILS-8?page=all ]
Thomas Dudziak resolved DDLUTILS-8.
---
Resolution: Fixed
The table copy approach is now implemented, and in the case of Sql Builder, for
tables with identity columns, a full table rebuild with data copying is
performed
MsSqlBuilder can't alter a table to make a column autoincremented (identity)
Key: DDLUTILS-8
URL: http://issues.apache.org/jira/browse/DDLUTILS-8
Project: DdlUtils
Issue Type: Bug
Components: Core - SqlServer
Reporter: Christoffer Hammarström
Assigned To: Thomas Dudziak
Fix For: 1.0
Attachments: DDLUTILS-8-1st-draft.patch, DDLUTILS-8-2nd-draft.patch
A column in an existing table can't be made autoincremented using ALTER TABLE.
I want to add this capability to MsSqlBuilder, but i'm not sure whether to
copy the approach of Microsoft Enterprise Manager, or if there is some better
way, and i would like some direction or input.
I've started by extracting methods alterTable() and alterColumns() from
alterDatabase() in SqlBuilder, and i'm overriding alterColumns() in
MsSqlBuilder with a check for autoincremented columns in the desiredTable but
not in the currentTable.
The approach used when scripting this change from Microsoft Enterprise
Manager is to:
1. Drop table constraints
2. Create a new replacement table with the name prefixed by 'Tmp_'
3. SET IDENTITY_INSERT Tmp_table ON
4. Copy the data from the table to the Tmp_table
5. Set IDENTITY_INSERT Tmp_table OFF
6. DROP TABLE table
7. EXECUTE sp_rename N'dbo.Tmp_table', N'table', 'OBJECT'
8. Readd table constraints
An example follows:
BEGIN TRANSACTION
SET QUOTED_IDENTIFIER ON
SET TRANSACTION ISOLATION LEVEL SERIALIZABLE
SET ARITHABORT ON
SET NUMERIC_ROUNDABORT OFF
SET CONCAT_NULL_YIELDS_NULL ON
SET ANSI_NULLS ON
SET ANSI_PADDING ON
SET ANSI_WARNINGS ON
COMMIT
BEGIN TRANSACTION
ALTER TABLE dbo.phones
DROP CONSTRAINT FK_phones_users
GO
COMMIT
BEGIN TRANSACTION
ALTER TABLE dbo.phones
DROP CONSTRAINT DF_phones_phonetype_id
GO
CREATE TABLE dbo.Tmp_phones
(
phone_id int NOT NULL IDENTITY (1, 1),
number varchar(25) NOT NULL,
user_id int NOT NULL,
phonetype_id int NOT NULL
) ON [PRIMARY]
GO
ALTER TABLE dbo.Tmp_phones ADD CONSTRAINT
DF_phones_phonetype_id DEFAULT (0) FOR phonetype_id
GO
SET IDENTITY_INSERT dbo.Tmp_phones ON
GO
IF EXISTS(SELECT * FROM dbo.phones)
EXEC('INSERT INTO dbo.Tmp_phones (phone_id, number, user_id, phonetype_id)
SELECT phone_id, number, user_id, phonetype_id FROM dbo.phones TABLOCKX')
GO
SET IDENTITY_INSERT dbo.Tmp_phones OFF
GO
DROP TABLE dbo.phones
GO
EXECUTE sp_rename N'dbo.Tmp_phones', N'phones', 'OBJECT'
GO
ALTER TABLE dbo.phones ADD CONSTRAINT
PK_phones PRIMARY KEY NONCLUSTERED
(
phone_id,
user_id
) ON [PRIMARY]
GO
ALTER TABLE dbo.phones WITH NOCHECK ADD CONSTRAINT
FK_phones_users FOREIGN KEY
(
user_id
) REFERENCES dbo.users
(
user_id
)
GO
COMMIT
--
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
[jira] Resolved: (DDLUTILS-89) Add support for ordering of foreign keys when reading from a live database
[ http://issues.apache.org/jira/browse/DDLUTILS-89?page=all ] Thomas Dudziak resolved DDLUTILS-89. Resolution: Fixed The platform interface has a new property foreignKeysSorted, and the two tasks (DatabaseToDdl, DdlToDatabase) have a related sortForeignKeys attribute, which - when set to true - force the alphabetical sorting of the foreign keys of the tables read from the database. Note that this does not affect the foreign keys of tables read from an XML file. Add support for ordering of foreign keys when reading from a live database -- Key: DDLUTILS-89 URL: http://issues.apache.org/jira/browse/DDLUTILS-89 Project: DdlUtils Issue Type: Improvement Components: Core (No specific database), Ant Tasks Environment: Oracle 10g EE SQLServer 2005 EE Windows XP SP2 Java 1.5.0_06 Reporter: Guy Davis Assigned To: Thomas Dudziak Fix For: 1.0 Attachments: order_fks.patch We use the WriteSchemaToFile task to store our applications schema in a file we place in our Subversion CM tool. Every time we run this task, it reorders the foreign keys on a table. So, for example, if Table A has FKs X, Y, Z then schema.xml file alternates between: table ... fk name='X' .../ fk name='Y' .../ fk name='Z' .../ /table AND table ... fk name='Z' .../ fk name='Y' .../ fk name='X' .../ /table Notice, that the keys haven't changed between schema dumps, just the ordering of them in the file. This means tracking version changes is more complicated as a developer's real changes are mixed in with these spurious key position changes. -- 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
[jira] Resolved: (DDLUTILS-114) decimal scale never gets written to schema-file in WriteSchema* Tasks
[ http://issues.apache.org/jira/browse/DDLUTILS-114?page=all ] Thomas Dudziak resolved DDLUTILS-114. - Resolution: Fixed decimal scale never gets written to schema-file in WriteSchema* Tasks - Key: DDLUTILS-114 URL: http://issues.apache.org/jira/browse/DDLUTILS-114 Project: DdlUtils Issue Type: Bug Components: Core (No specific database) Reporter: Andreas Wurzer Assigned To: Thomas Dudziak Fix For: 1.0 Attachments: scale-fix.diff when doing writeSchemaToFile (or other writeSchema Task), the scale of a decimal column never gets written to the schema file -- 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
[jira] Resolved: (DDLUTILS-43) jdbc model reader does not set the database name
[ http://issues.apache.org/jira/browse/DDLUTILS-43?page=all ] Thomas Dudziak resolved DDLUTILS-43. Resolution: Fixed The name is now taken from the catalog read from the database metadata, or it can be supplied to both the API and the Ant task. If there are specific databases where the catalog approach does not work, then please open a new issue specific for these databases. jdbc model reader does not set the database name Key: DDLUTILS-43 URL: http://issues.apache.org/jira/browse/DDLUTILS-43 Project: DdlUtils Issue Type: Bug Components: Core (No specific database) Reporter: Thorbjørn Ravn Andersen Assigned To: Thomas Dudziak Fix For: 1.0 On 11/7/05, Thorbjørn Ravn Andersen [EMAIL PROTECTED] wrote: I just noticed that the method described to read from a database, put together with the method to write to XML does not produce XML-files that can be read in again with the method to read from xml. I found that a database.setName(whatever) had to be called before writing to xml to remidy this. You're right, the jdbc model reader does not set the database name yet. Could you file an issue with JIRA ? Tom -- 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
[jira] Resolved: (DDLUTILS-20) Oracle FLOAT and DOUBLE type mappings have zero scale
[ http://issues.apache.org/jira/browse/DDLUTILS-20?page=all ] Thomas Dudziak resolved DDLUTILS-20. Resolution: Fixed DdlUtils now uses DOUBLE PRECISION, FLOAT and REAL respectively for these types as these are available at least in Oracle 8 and newer. Oracle FLOAT and DOUBLE type mappings have zero scale - Key: DDLUTILS-20 URL: http://issues.apache.org/jira/browse/DDLUTILS-20 Project: DdlUtils Issue Type: Bug Components: Core - Oracle Reporter: Richard Bounds Assigned To: Thomas Dudziak Fix For: 1.0 Attachments: metadata.xml In Oracle8Platform, the types FLOAT and DOUBLE are mapped to NUMBER(38). According to Oracle's docs, this type has zero scale. It looks like floating point numbers should be specified either as just NUMBER or FLOAT(n). See: http://oraclelon1.oracle.com/docs/cd/B19306_01/server.102/b14200/sql_elements001.htm#g196646 -- 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
[jira] Resolved: (DDLUTILS-18) DB2 autoincrement
[ http://issues.apache.org/jira/browse/DDLUTILS-18?page=all ] Thomas Dudziak resolved DDLUTILS-18. Resolution: Fixed A table defined as CREATE TABLE Test ( PK INTEGER NOT NULL GENERATED BY DEFAULT AS IDENTITY, PRIMARY KEY (PK) ) is now returned as table name=TEST column name=PK primaryKey=true required=true type=INTEGER size=10 autoIncrement=true/ /table The same applies to a table defined as CREATE TABLE Test ( PK INTEGER NOT NULL GENERATED ALWAYS AS IDENTITY, PRIMARY KEY (PK) ) though DdlUtils will not generate this form of identity. DB2 autoincrement - Key: DDLUTILS-18 URL: http://issues.apache.org/jira/browse/DDLUTILS-18 Project: DdlUtils Issue Type: Bug Components: Core - DB2 Environment: DB2 version 8 Reporter: dan meany Assigned To: Thomas Dudziak Fix For: 1.0 Reading table schema for an autoincrement column in DB2 v.8 produces: column name=SEQ_NO primaryKey=true required=true type=INTEGER size=10 default=IDENTITY GENERATED BY DEFAULT autoIncrement=false/ Should be autoIncrement=true -- 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
[jira] Commented: (DDLUTILS-63) ddltoDatabase errors due to specific string values in table rows of data.xml -- ddltoDatabase(to MySQL) using files produced by databaseToDdl(from MSSQL)
[ http://issues.apache.org/jira/browse/DDLUTILS-63?page=comments#action_12422035 ] Thomas Dudziak commented on DDLUTILS-63: Could you state the row as it is in the database (e.g. copied from a sql tool) ? I'm not quite sure whether the reading of data from the database or the writing to XML is in error here. ddltoDatabase errors due to specific string values in table rows of data.xml -- ddltoDatabase(to MySQL) using files produced by databaseToDdl(from MSSQL) -- Key: DDLUTILS-63 URL: http://issues.apache.org/jira/browse/DDLUTILS-63 Project: DdlUtils Issue Type: Bug Components: Core (No specific database) Environment: Win 2K SQL Server jtds MySQL 5.0 MySQL Connector/J Reporter: Appajee Papolu Assigned To: Thomas Dudziak Fix For: 1.0 - Dumped out a MSSQL database using ddlutils ant task - Used the resulting files to create a database in MySQL - Getting errors while importing data that have embedded XML data in their row data, for example, as in: whatever-table col1=78 col2=name col2=Set-schema: User#1;$%$#10;Query: #2; '104' LIKE quot;$GID$;%quot; OR '104' LIKE quot;%;$GID$;%quot; OR '104' LIKE quot;% $GID$;%quot;#10;Entry-list: #10;window-position: 0518 0145 0395 0326#10;end#10;/ - Receiving error as follows: [ddlToDatabase] Jan 20, 2006 7:36:58 AM org.apache.commons.digester.Digester fatalError [ddlToDatabase] SEVERE: Parse Fatal Error at line 1705 column 107: Character reference #1 is an invalid XML character. [ddlToDatabase] org.xml.sax.SAXParseException: Character reference #1 is an invalid XML character. -- 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
[jira] Resolved: (DDLUTILS-14) Sybase autoincrement column
[ http://issues.apache.org/jira/browse/DDLUTILS-14?page=all ] Thomas Dudziak resolved DDLUTILS-14. Resolution: Fixed Sybase auto-increment reading should work now. Could you perhaps run that again (I don't have a Sybase installation at the moment) ? Sybase autoincrement column --- Key: DDLUTILS-14 URL: http://issues.apache.org/jira/browse/DDLUTILS-14 Project: DdlUtils Issue Type: Bug Components: Core - Sybase Environment: Sybase Reporter: dan meany Assigned To: Thomas Dudziak Fix For: 1.0 Reading a Sybase ASA schema with an autoincrement column produces default=autoincrement autoIncrement=false instead of autoIncrement=true -- 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
[jira] Commented: (DDLUTILS-61) 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-61?page=comments#action_12422037
]
Thomas Dudziak commented on DDLUTILS-61:
Could you state the row as it is in the database, e.g by copying from some SQL
tool ? I'm interested in the default value as it is in the database.
You can also try to run your test again, as I've made some changes to strip
away stuff that Sql Server adds to the concrete default value, like parentheses.
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
Issue Type: Bug
Components: Core - SqlServer
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
- 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
[jira] Resolved: (DDLUTILS-50) FK Constraints Failing on Merge in MS-SQL
[ http://issues.apache.org/jira/browse/DDLUTILS-50?page=all ] Thomas Dudziak resolved DDLUTILS-50. Resolution: Fixed This now works (with the revised database alteration algorithm). Actually, now there won't be any SQL executed (as it should be because the DB did not change): [ddlToDatabase] INFO: Executed 0 SQL command(s) with 0 error(s) FK Constraints Failing on Merge in MS-SQL - Key: DDLUTILS-50 URL: http://issues.apache.org/jira/browse/DDLUTILS-50 Project: DdlUtils Issue Type: Bug Components: Core - SqlServer Environment: WinXP Pro, SQL Server 2000, Java 1.4.2 Reporter: Colin Ritchie Assigned To: Thomas Dudziak Fix For: 1.0 Re-running the writeSchemaToDatabase task on an existing MS-SQL database causes errors on all the foreign-key nodes, reporting the error There is already an object named 'name' in the database. Snippet of my schema: table name=oci_schedules column name=schd_m_id primaryKey=false required=true type=INTEGER default=0 autoIncrement=false/ foreign-key foreignTable=oci_schedule_modes reference local=schd_m_id foreign=schd_m_id/ /foreign-key /table table name=oci_schedule_modes column name=schd_m_id primaryKey=true required=true type=INTEGER autoIncrement=true description=auto_increment/ /table Error: [ddlToDatabase] SQL Command ALTER TABLE oci_schedules [ddlToDatabase] ADD CONSTRAINT oci_schedules_FK_schd_m_id_oci_schedule_modes FOREIGN KEY (schd_m_id) REFERENCESoci_schedule_modes (schd_m_id) failed with [Microsoft][SQLServer 2000 Driver for JDBC][SQLServer]There is already an object named 'oci_schedules_FK_schd_m_id_oci_schedule_modes' in the database. I have tried this using the open source JTDS 1.1, with the same error message. I have also tried specifying the foreign key name in the XML node, with the same result. -- 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
[jira] Resolved: (DDLUTILS-51) BOOLEANINT for MS-SQL desires TINYINT, but uses SMALLINT
[ http://issues.apache.org/jira/browse/DDLUTILS-51?page=all ] Thomas Dudziak resolved DDLUTILS-51. Resolution: Fixed This works now, DdlUtils will not change the column if you run the schema against the database again: [ddlToDatabase] INFO: Executed 0 SQL command(s) with 0 error(s) BOOLEANINT for MS-SQL desires TINYINT, but uses SMALLINT Key: DDLUTILS-51 URL: http://issues.apache.org/jira/browse/DDLUTILS-51 Project: DdlUtils Issue Type: Bug Components: Core - SqlServer Environment: WinXP Pro, SQL-Server 2000, java 1.4.2 Reporter: Colin Ritchie Assigned To: Thomas Dudziak Priority: Minor Fix For: 1.0 Columns for MS-SQL with Type BOOLEANINT get the following error when using the ant task writeSchemaToDatabase: [ddlToDatabase] INFO: Altering column oci_schedules.schd_state [ddlToDatabase] INFO: desired = Column [name=schd_state; javaName=null; type=TINYINT; typeCode=-6; size=null; required=false; primaryKey=false; autoIncrement=false; defaultValue=null; precisionRadix=0; scale=0] [ddlToDatabase] INFO: current = Column [name=schd_state; javaName=null; type=SMALLINT; typeCode=5; size=5; required=false; primaryKey=false; autoIncrement=false; defaultValue=null; precisionRadix=5; scale=0] The following is a snippet of my configuration file: table name=oci_schedules column name=schd_state primaryKey=false required=false type=BOOLEANINT autoIncrement=false/ /table -- 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
[jira] Updated: (DDLUTILS-118) Modifying columns generates wrong SQL statement
[ http://issues.apache.org/jira/browse/DDLUTILS-118?page=all ] Niklas Ekman updated DDLUTILS-118: -- Description: When changing a column size the following SQL statement is generated: ALTER TABLE testtable MODIFY test VARCHAR(100) But according to the PostgreSQL manual it should look like ALTER TABLE testtable ALTER COLUMN test TYPE VARCHAR(111) was: When changing a column size the following SQL statement is generated: ALTER TABLE testtable MODIFY test VARCHAR(100) But according to the PostgreSQL manual it should look like ALTER TABLE fields ALTER COLUMN test TYPE VARCHAR(111) Modifying columns generates wrong SQL statement --- Key: DDLUTILS-118 URL: http://issues.apache.org/jira/browse/DDLUTILS-118 Project: DdlUtils Issue Type: Bug Components: Core - PostgreSql Environment: PostgreSQL Database Server 8.1, Windows XP SP2, JDBC driver version 8.1-407 JDBC3 Reporter: Niklas Ekman Assigned To: Thomas Dudziak Priority: Minor When changing a column size the following SQL statement is generated: ALTER TABLE testtable MODIFY test VARCHAR(100) But according to the PostgreSQL manual it should look like ALTER TABLE testtable ALTER COLUMN test TYPE VARCHAR(111) -- 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
[jira] Commented: (DDLUTILS-118) Modifying columns generates wrong SQL statement
[ http://issues.apache.org/jira/browse/DDLUTILS-118?page=comments#action_12422775 ] Thomas Dudziak commented on DDLUTILS-118: - Are you sure that you're using the correct platform and/or current version of DdlUtils ? The PostgreSQL platform does not use a column modification statement at all as it is too limited on the PostgreSQL database. It only uses PostgreSQL specific DDL statements for adding and removing columns: http://svn.apache.org/viewvc/db/ddlutils/trunk/src/java/org/apache/ddlutils/platform/postgresql/PostgreSqlBuilder.java?view=markup Modifying columns generates wrong SQL statement --- Key: DDLUTILS-118 URL: http://issues.apache.org/jira/browse/DDLUTILS-118 Project: DdlUtils Issue Type: Bug Components: Core - PostgreSql Environment: PostgreSQL Database Server 8.1, Windows XP SP2, JDBC driver version 8.1-407 JDBC3 Reporter: Niklas Ekman Assigned To: Thomas Dudziak Priority: Minor When changing a column size the following SQL statement is generated: ALTER TABLE testtable MODIFY test VARCHAR(100) But according to the PostgreSQL manual it should look like ALTER TABLE testtable ALTER COLUMN test TYPE VARCHAR(111) -- 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
[jira] Commented: (DDLUTILS-118) Modifying columns generates wrong SQL statement
[ http://issues.apache.org/jira/browse/DDLUTILS-118?page=comments#action_12422923 ] Niklas Ekman commented on DDLUTILS-118: --- I'm using the DdlUtils trunk, newly checked out and built with ant. And also, I've checked that it is the org.apache.ddlutils.platform.postgresql.PostgreSqlBuilder that's used when I call PlatformFactory.createNewPlatformInstance(dataSource) (I called platform.getSqlBuilder().getClass().getName() to find out). According to the help file for PostgreSQL 8.1 the following statement is used for modifying columns: ALTER TABLE [ ONLY ] name [ * ] action [, ... ] where action is one of: ALTER [ COLUMN ] column TYPE type [ USING expression ] . Examples To change the types of two existing columns in one operation: ALTER TABLE distributors ALTER COLUMN address TYPE varchar(80), ALTER COLUMN name TYPE varchar(100); This is directly from the help file, I've stripped away stuff that's not important. Modifying columns generates wrong SQL statement --- Key: DDLUTILS-118 URL: http://issues.apache.org/jira/browse/DDLUTILS-118 Project: DdlUtils Issue Type: Bug Components: Core - PostgreSql Environment: PostgreSQL Database Server 8.1, Windows XP SP2, JDBC driver version 8.1-407 JDBC3 Reporter: Niklas Ekman Assigned To: Thomas Dudziak Priority: Minor When changing a column size the following SQL statement is generated: ALTER TABLE testtable MODIFY test VARCHAR(100) But according to the PostgreSQL manual it should look like ALTER TABLE testtable ALTER COLUMN test TYPE VARCHAR(111) -- 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
[jira] Created: (DDLUTILS-119) Dropping unique index properly on SQL Server.
Dropping unique index properly on SQL Server. - Key: DDLUTILS-119 URL: http://issues.apache.org/jira/browse/DDLUTILS-119 Project: DdlUtils Issue Type: Bug Components: Core - SqlServer Affects Versions: 1.0 Reporter: Jun Li Assigned To: Thomas Dudziak On SQL Server, some unique indexes are created automatically to enforce the UNIQUE constraint. For this kind of unique index, we cannot use DROP INDEX command to remove them, should use ALTER TABLE table_name DROP CONSTRAINT index_name instead. -- 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
[jira] Resolved: (DDLUTILS-118) Modifying columns generates wrong SQL statement
[ http://issues.apache.org/jira/browse/DDLUTILS-118?page=all ] Thomas Dudziak resolved DDLUTILS-118. - Resolution: Fixed This only appeared when using writeSchemaSqlToFile, which for some reason used the old alteration algorithm. I've removed this old algorithm, and now the correct SQL is generated. Modifying columns generates wrong SQL statement --- Key: DDLUTILS-118 URL: http://issues.apache.org/jira/browse/DDLUTILS-118 Project: DdlUtils Issue Type: Bug Components: Core - PostgreSql Environment: PostgreSQL Database Server 8.1, Windows XP SP2, JDBC driver version 8.1-407 JDBC3 Reporter: Niklas Ekman Assigned To: Thomas Dudziak Priority: Minor When changing a column size the following SQL statement is generated: ALTER TABLE testtable MODIFY test VARCHAR(100) But according to the PostgreSQL manual it should look like ALTER TABLE testtable ALTER COLUMN test TYPE VARCHAR(111) -- 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
[jira] Resolved: (DDLUTILS-120) Update the alterTable signature
[ http://issues.apache.org/jira/browse/DDLUTILS-120?page=all ] Thomas Dudziak resolved DDLUTILS-120. - Resolution: Fixed Update the alterTable signature --- Key: DDLUTILS-120 URL: http://issues.apache.org/jira/browse/DDLUTILS-120 Project: DdlUtils Issue Type: Bug Components: Core (No specific database) Reporter: Thomas Dudziak Assigned To: Thomas Dudziak Fix For: 1.0 The alterTables method signatures still contain boolean flags like doDrops which are not used anymore -- 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
[jira] Updated: (DDLUTILS-63) ddltoDatabase errors due to specific string values in table rows of data.xml -- ddltoDatabase(to MySQL) using files produced by databaseToDdl(from MSSQL)
[ http://issues.apache.org/jira/browse/DDLUTILS-63?page=all ] Appajee Papolu updated DDLUTILS-63: --- Attachment: RowWithAsciiOneChar.txt This file shows an exported row with one column that has some proprietary encoded text -- which has an ASCII - 1 as a separator character within the encoded data. ddltoDatabase errors due to specific string values in table rows of data.xml -- ddltoDatabase(to MySQL) using files produced by databaseToDdl(from MSSQL) -- Key: DDLUTILS-63 URL: http://issues.apache.org/jira/browse/DDLUTILS-63 Project: DdlUtils Issue Type: Bug Components: Core (No specific database) Environment: Win 2K SQL Server jtds MySQL 5.0 MySQL Connector/J Reporter: Appajee Papolu Assigned To: Thomas Dudziak Fix For: 1.0 Attachments: RowWithAsciiOneChar.txt - Dumped out a MSSQL database using ddlutils ant task - Used the resulting files to create a database in MySQL - Getting errors while importing data that have embedded XML data in their row data, for example, as in: whatever-table col1=78 col2=name col2=Set-schema: User#1;$%$#10;Query: #2; '104' LIKE quot;$GID$;%quot; OR '104' LIKE quot;%;$GID$;%quot; OR '104' LIKE quot;% $GID$;%quot;#10;Entry-list: #10;window-position: 0518 0145 0395 0326#10;end#10;/ - Receiving error as follows: [ddlToDatabase] Jan 20, 2006 7:36:58 AM org.apache.commons.digester.Digester fatalError [ddlToDatabase] SEVERE: Parse Fatal Error at line 1705 column 107: Character reference #1 is an invalid XML character. [ddlToDatabase] org.xml.sax.SAXParseException: Character reference #1 is an invalid XML character. -- 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
[jira] Created: (DDLUTILS-122) Foreign keys not generated in SQL
Foreign keys not generated in SQL
-
Key: DDLUTILS-122
URL: http://issues.apache.org/jira/browse/DDLUTILS-122
Project: DdlUtils
Issue Type: Bug
Components: Core - DB2
Affects Versions: 1.0
Reporter: Mike Perham
Assigned To: Thomas Dudziak
Priority: Critical
Attachments: fabric-schema.sql, fabric-schema.xml
I'm using writeSchemaSqlToFile to generate the SQL from my schema file:
{code:xml}
target name=schema-to-sql
taskdef name=ddl2Database
classname=org.apache.ddlutils.task.DdlToDatabaseTask
classpathref=runtime-classpath/
ddl2Database databaseType=db2 schemaFile=fabric-schema.xml
writeSchemaSqlToFile alterDatabase=false doDrops=false
failOnError=true outputFile=fabric-schema.sql /
/ddl2Database
/target
{code}
See attached schema xml and sql. The schema was generated from mysql 5.0.19
using the 5.0.3 JDBC driver. The SQL is being generated for DB2. Note that
the schema includes plenty of foreign key references but the generated SQL
includes none of them. This is a blocker for us to use DdlUtils.
--
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
[jira] Created: (DDLUTILS-123) Allow long table/column names in DB2 8.0+
Allow long table/column names in DB2 8.0+ - Key: DDLUTILS-123 URL: http://issues.apache.org/jira/browse/DDLUTILS-123 Project: DdlUtils Issue Type: Improvement Components: Core - DB2 Affects Versions: 1.0 Reporter: Mike Perham Assigned To: Thomas Dudziak DB2 8.0 and above support table and column names up to 64 characters. We have a few tables which require greater than 18 charater names and would like to disable DdlUtils' mangling of the names. -- 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
[jira] Created: (DDLUTILS-124) Patch to fix Maven 2 build
Patch to fix Maven 2 build -- Key: DDLUTILS-124 URL: http://issues.apache.org/jira/browse/DDLUTILS-124 Project: DdlUtils Issue Type: Bug Components: Build Affects Versions: 1.0 Reporter: Mike Perham Assigned To: Thomas Dudziak Attachments: build.patch This is a patch to get the DdlUtils build working with Maven 2. I am a Maven PMC member so I hope this helps. :-) Note there are a bunch of test failures. It is using hsqldb 1.8.0.4 for tests and this obviously could fail if you were depending on behavior in 1.7.x.x. -- 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
[jira] Commented: (DDLUTILS-122) Foreign keys not generated in SQL
[
http://issues.apache.org/jira/browse/DDLUTILS-122?page=comments#action_12428569
]
Thomas Dudziak commented on DDLUTILS-122:
-
I'm not sure what you mean ? The attached SQL script includes plenty of foreign
keys (47 to be precise) at the end of the file, which are of the form:
ALTER TABLE localTableName
ADD CONSTRAINT foreignKeyName FOREIGN KEY (localColumns) REFERENCES
remoteTableName (remoteColumns);
Foreign keys not generated in SQL
-
Key: DDLUTILS-122
URL: http://issues.apache.org/jira/browse/DDLUTILS-122
Project: DdlUtils
Issue Type: Bug
Components: Core - DB2
Affects Versions: 1.0
Reporter: Mike Perham
Assigned To: Thomas Dudziak
Priority: Critical
Attachments: fabric-schema.sql, fabric-schema.xml
I'm using writeSchemaSqlToFile to generate the SQL from my schema file:
{code:xml}
target name=schema-to-sql
taskdef name=ddl2Database
classname=org.apache.ddlutils.task.DdlToDatabaseTask
classpathref=runtime-classpath/
ddl2Database databaseType=db2 schemaFile=fabric-schema.xml
writeSchemaSqlToFile alterDatabase=false doDrops=false
failOnError=true outputFile=fabric-schema.sql /
/ddl2Database
/target
{code}
See attached schema xml and sql. The schema was generated from mysql 5.0.19
using the 5.0.3 JDBC driver. The SQL is being generated for DB2. Note that
the schema includes plenty of foreign key references but the generated SQL
includes none of them. This is a blocker for us to use DdlUtils.
--
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
[jira] Updated: (DDLUTILS-124) Patch to fix Maven 2 build
[ http://issues.apache.org/jira/browse/DDLUTILS-124?page=all ] Thomas Dudziak updated DDLUTILS-124: Fix Version/s: 1.0 Patch to fix Maven 2 build -- Key: DDLUTILS-124 URL: http://issues.apache.org/jira/browse/DDLUTILS-124 Project: DdlUtils Issue Type: Bug Components: Build Affects Versions: 1.0 Reporter: Mike Perham Assigned To: Martin van den Bemt Fix For: 1.0 Attachments: build.patch This is a patch to get the DdlUtils build working with Maven 2. I am a Maven PMC member so I hope this helps. :-) Note there are a bunch of test failures. It is using hsqldb 1.8.0.4 for tests and this obviously could fail if you were depending on behavior in 1.7.x.x. -- 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
[jira] Assigned: (DDLUTILS-124) Patch to fix Maven 2 build
[ http://issues.apache.org/jira/browse/DDLUTILS-124?page=all ] Thomas Dudziak reassigned DDLUTILS-124: --- Assignee: Martin van den Bemt (was: Thomas Dudziak) Patch to fix Maven 2 build -- Key: DDLUTILS-124 URL: http://issues.apache.org/jira/browse/DDLUTILS-124 Project: DdlUtils Issue Type: Bug Components: Build Affects Versions: 1.0 Reporter: Mike Perham Assigned To: Martin van den Bemt Fix For: 1.0 Attachments: build.patch This is a patch to get the DdlUtils build working with Maven 2. I am a Maven PMC member so I hope this helps. :-) Note there are a bunch of test failures. It is using hsqldb 1.8.0.4 for tests and this obviously could fail if you were depending on behavior in 1.7.x.x. -- 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
[jira] Commented: (DDLUTILS-122) Foreign keys not generated in SQL
[
http://issues.apache.org/jira/browse/DDLUTILS-122?page=comments#action_12428570
]
Mike Perham commented on DDLUTILS-122:
--
Wow, I feel idiotic. Ok, you put them at the end so you don't have to worry
about ordering. You can close this. :)
Foreign keys not generated in SQL
-
Key: DDLUTILS-122
URL: http://issues.apache.org/jira/browse/DDLUTILS-122
Project: DdlUtils
Issue Type: Bug
Components: Core - DB2
Affects Versions: 1.0
Reporter: Mike Perham
Assigned To: Thomas Dudziak
Priority: Critical
Attachments: fabric-schema.sql, fabric-schema.xml
I'm using writeSchemaSqlToFile to generate the SQL from my schema file:
{code:xml}
target name=schema-to-sql
taskdef name=ddl2Database
classname=org.apache.ddlutils.task.DdlToDatabaseTask
classpathref=runtime-classpath/
ddl2Database databaseType=db2 schemaFile=fabric-schema.xml
writeSchemaSqlToFile alterDatabase=false doDrops=false
failOnError=true outputFile=fabric-schema.sql /
/ddl2Database
/target
{code}
See attached schema xml and sql. The schema was generated from mysql 5.0.19
using the 5.0.3 JDBC driver. The SQL is being generated for DB2. Note that
the schema includes plenty of foreign key references but the generated SQL
includes none of them. This is a blocker for us to use DdlUtils.
--
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
[jira] Commented: (DDLUTILS-122) Foreign keys not generated in SQL
[
http://issues.apache.org/jira/browse/DDLUTILS-122?page=comments#action_12428571
]
Thomas Dudziak commented on DDLUTILS-122:
-
No need to feel idiotic, we all make such mistakes :-) Though you might bring
things like this up on the user mailing list first where it is likely to get
you faster responses.
Foreign keys not generated in SQL
-
Key: DDLUTILS-122
URL: http://issues.apache.org/jira/browse/DDLUTILS-122
Project: DdlUtils
Issue Type: Bug
Components: Core - DB2
Affects Versions: 1.0
Reporter: Mike Perham
Assigned To: Thomas Dudziak
Priority: Critical
Attachments: fabric-schema.sql, fabric-schema.xml
I'm using writeSchemaSqlToFile to generate the SQL from my schema file:
{code:xml}
target name=schema-to-sql
taskdef name=ddl2Database
classname=org.apache.ddlutils.task.DdlToDatabaseTask
classpathref=runtime-classpath/
ddl2Database databaseType=db2 schemaFile=fabric-schema.xml
writeSchemaSqlToFile alterDatabase=false doDrops=false
failOnError=true outputFile=fabric-schema.sql /
/ddl2Database
/target
{code}
See attached schema xml and sql. The schema was generated from mysql 5.0.19
using the 5.0.3 JDBC driver. The SQL is being generated for DB2. Note that
the schema includes plenty of foreign key references but the generated SQL
includes none of them. This is a blocker for us to use DdlUtils.
--
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
[jira] Created: (DDLUTILS-125) Add support for START WITH
Add support for START WITH Key: DDLUTILS-125 URL: http://issues.apache.org/jira/browse/DDLUTILS-125 Project: DdlUtils Issue Type: New Feature Components: Core (No specific database) Affects Versions: 1.0 Reporter: Mike Perham Assigned To: Thomas Dudziak OJB requires all identity column values to be greater than 0. Most databases default the starting value to 0. I would like to be able to set a default for all sequences/identities that I create. Maybe a new attribute on database like default-start-with. -- 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
[jira] Updated: (DDLUTILS-126) errors about the sequence with postgresql
[ http://issues.apache.org/jira/browse/DDLUTILS-126?page=all ]
Rusty Wright updated DDLUTILS-126:
--
Description:
Ant output:
==
[ddlToDatabase] Read schema file
/local_a/users/rusty/java/jwaitlistd10/sql/waitlist.xml
[ddlToDatabase] Aug 24, 2006 12:47:57 PM
org.apache.ddlutils.alteration.ModelComparator compare
[ddlToDatabase] INFO: Table waitlist needs to be added
[ddlToDatabase] Aug 24, 2006 12:47:57 PM
org.apache.ddlutils.platform.PlatformImplBase evaluateBatch
[ddlToDatabase] WARNING: SQL Command CREATE TABLE waitlist
[ddlToDatabase] (
[ddlToDatabase] waitlist_key BIGINT NOT NULL UNIQUE DEFAULT
nextval('waitlist_waitlist_key_seq'),
[ddlToDatabase] facility VARCHAR(20) NOT NULL,
[ddlToDatabase] uid VARCHAR(16) NOT NULL,
[ddlToDatabase] cn VARCHAR(40) NOT NULL,
[ddlToDatabase] type VARCHAR(20) NOT NULL,
[ddlToDatabase] platform VARCHAR(8) NOT NULL,
[ddlToDatabase] signin_time TIMESTAMP NOT NULL,
[ddlToDatabase] PRIMARY KEY (waitlist_key)
[ddlToDatabase] ) failed with: ERROR: relation waitlist_waitlist_key_seq does
not exist
[ddlToDatabase] Aug 24, 2006 12:47:57 PM
org.apache.ddlutils.platform.PlatformImplBase evaluateBatch
[ddlToDatabase] WARNING: SQL Command CREATE UNIQUE INDEX uid_platform_facility
ON waitlist (uid, platform, facility) failed with: ERROR: relation waitlist
does not exist
[ddlToDatabase] Aug 24, 2006 12:47:57 PM
org.apache.ddlutils.platform.PlatformImplBase evaluateBatch
[ddlToDatabase] INFO: Executed 2 SQL command(s) with 2 error(s)
[ddlToDatabase] Written schema to database
[ddlToDatabase] Read schema file
/local_a/users/rusty/java/jwaitlistd10/sql/waitlist2.xml
[ddlToDatabase] Written SQL to
/local_a/users/rusty/java/jwaitlistd10/sql/waitlist2_generated.sql
==
waitlist.xml file:
==
?xml version=1.0?
!DOCTYPE database SYSTEM http://db.apache.org/torque/dtd/database.dtd;
database name=waitlist defaultIdMethod=native
table name=waitlist
column name=waitlist_key
type=bigint
size=20
required=true
primaryKey=true
autoIncrement=true
/
column name=facility
type=varchar
size=20
required=true
/
column name=uid
type=varchar
size=16
required=true
/
column name=cn
type=varchar
size=40
required=true
/
column name=type
type=varchar
size=20
required=true
/
column name=platform
type=varchar
size=8
required=true
/
column name=signin_time
type=timestamp
required=true
/
unique name=uid_platform_facility
unique-column name=uid /
unique-column name=platform /
unique-column name=facility /
/unique
/table
/database
was:
Ant output:
==
[ddlToDatabase] Read schema file
/local_a/users/rusty/java/jwaitlistd10/sql/waitlist.xml
[ddlToDatabase] Aug 24, 2006 12:47:57 PM
org.apache.ddlutils.alteration.ModelComparator compare
[ddlToDatabase] INFO: Table waitlist needs to be added
[ddlToDatabase] Aug 24, 2006 12:47:57 PM
org.apache.ddlutils.platform.PlatformImplBase evaluateBatch
[ddlToDatabase] WARNING: SQL Command CREATE TABLE waitlist
[ddlToDatabase] (
[ddlToDatabase] waitlist_key BIGINT NOT NULL UNIQUE DEFAULT
nextval('waitlist_waitlist_key_seq'),
[ddlToDatabase] facility VARCHAR(20) NOT NULL,
[ddlToDatabase] uid VARCHAR(16) NOT NULL,
[ddlToDatabase] cn VARCHAR(40) NOT NULL,
[ddlToDatabase] type VARCHAR(20) NOT NULL,
[ddlToDatabase] platform VARCHAR(8) NOT NULL,
[ddlToDatabase] signin_time TIMESTAMP NOT NULL,
[ddlToDatabase] PRIMARY KEY (waitlist_key)
[ddlToDatabase] ) failed with: ERROR: relation waitlist_waitlist_key_seq does
not exist
[ddlToDatabase] Aug 24, 2006 12:47:57 PM
org.apache.ddlutils.platform.PlatformImplBase evaluateBatch
[ddlToDatabase] WARNING: SQL Command CREATE UNIQUE INDEX uid_platform_facility
ON waitlist (uid, platform, facility) failed with: ERROR: relation waitlist
does not exist
[ddlToDatabase] Aug 24, 2006 12:47:57 PM
org.apache.ddlutils.platform.PlatformImplBase evaluateBatch
[ddlToDatabase] INFO: Executed 2 SQL command(s) with 2 error(s)
[ddlToDatabase] Written schema to database
[ddlToDatabase] Read schema file
/local_a/users/rusty/java/jwaitlistd10/sql/waitlist2.xml
[ddlToDatabase] Written SQL to
/local_a/users/rusty/java/jwaitlistd10/sql/waitlist2_generated.sql
==
waitlist2.xml file:
==
?xml version=1.0?
!DOCTYPE database SYSTEM http://db.apache.org/torque/dtd/database.dtd;
database name=waitlist defaultIdMethod=native
table name=waitlist
column name=waitlist_key
[jira] Commented: (DDLUTILS-85) Add support for unique constraints
[ http://issues.apache.org/jira/browse/DDLUTILS-85?page=comments#action_12437610 ] John Fereira commented on DDLUTILS-85: -- I couldn't tell what the resolution status was for this issue... Using a McKoi database I created a database table with a unique key using the following SQL: CREATE TABLE NOTIFICATION_CONTENT_TYPES ( ID INTEGER NOT NULL, NAME VARCHAR(500) NOT NULL, DESCRIPTION VARCHAR(1000) NOT NULL, NAMESPACE VARCHAR(1000) NOT NULL ) ; ALTER TABLE NOTIFICATION_CONTENT_TYPES ADD CONSTRAINT NOTIFICATION_CONTENT_TYPE_PK PRIMARY KEY (ID); ALTER TABLE NOTIFICATION_CONTENT_TYPES ADD CONSTRAINT NOTIFICATION_CONTENT_TYPE_UK1 UNIQUE (NAME); If I export the database to XML it produces the following: table name=NOTIFICATION_CONTENT_TYPES column name=ID primaryKey=true required=true type=INTEGER size=1024 autoIncrement=false/ column name=NAME primaryKey=false required=true type=VARCHAR size=500 autoIncrement=false/ column name=DESCRIPTION primaryKey=false required=true type=VARCHAR size=1000 autoIncrement=false/ column name=NAMESPACE primaryKey=false required=true type=VARCHAR size=1000 autoIncrement=false/ unique name=NOTIFICATION_CONTENT_TYPE_UK1 unique-column name=NAME/ /unique /table If I subsequently use that XML to recreate the table it doesn't appear as if the UNIQUE key is created (a subsequent export produces XML without the unique element. Add support for unique constraints -- Key: DDLUTILS-85 URL: http://issues.apache.org/jira/browse/DDLUTILS-85 Project: DdlUtils Issue Type: New Feature Components: Core (No specific database) Reporter: Przemyslaw Sztoch Assigned To: Thomas Dudziak Fix For: 1.1 For example in PostgreSQL we can create CONSTRAINT or INDEX. What will be generated, should be set somewhere in model or config. -- 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
[jira] Resolved: (DDLUTILS-46) Schemas dumped from DB2/400 tries twice to create primary key when loaded to Derby
[ http://issues.apache.org/jira/browse/DDLUTILS-46?page=all ] Thomas Dudziak resolved DDLUTILS-46. Resolution: Fixed I think the problem was fixed during the re-work of the platforms. If it is still there though, then please re-open the bug. Schemas dumped from DB2/400 tries twice to create primary key when loaded to Derby -- Key: DDLUTILS-46 URL: http://issues.apache.org/jira/browse/DDLUTILS-46 Project: DdlUtils Issue Type: Improvement Components: Core - DB2 Reporter: Thorbjørn Ravn Andersen Assigned To: Thomas Dudziak Priority: Minor Fix For: 1.0 I dump a schema from a DB2/400 machine. All tables which have a primary key also lists the primary key as a unique index: unique name=TBLACCESSMODULE unique-column name=ID/ /unique When the schema is loaded into Oracle, Oracle complains when trying to make the index, with an error (cannot reproduce right now) to the effect that the unique index does already exist. Presumably because the primary key was created along with the table. Perhaps PK's should be filterered out from the unique indexes? -- 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
[jira] Resolved: (DDLUTILS-61) 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-61?page=all ]
Thomas Dudziak resolved DDLUTILS-61.
Resolution: Fixed
This should be fixed (as noted in my previous comment).
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
Issue Type: Bug
Components: Core - SqlServer
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
- 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
[jira] Resolved: (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=all ]
Thomas Dudziak resolved DDLUTILS-62.
Resolution: Fixed
This should be fixed (similar to DDLUTILS-61).
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 '('apos;some stringapos;')' 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
[jira] Resolved: (DDLUTILS-63) ddltoDatabase errors due to specific string values in table rows of data.xml -- ddltoDatabase(to MySQL) using files produced by databaseToDdl(from MSSQL)
[ http://issues.apache.org/jira/browse/DDLUTILS-63?page=all ] Thomas Dudziak resolved DDLUTILS-63. Resolution: Fixed Values that contain such characters are now always written to sub elements, and Base64-encoded. ddltoDatabase errors due to specific string values in table rows of data.xml -- ddltoDatabase(to MySQL) using files produced by databaseToDdl(from MSSQL) -- Key: DDLUTILS-63 URL: http://issues.apache.org/jira/browse/DDLUTILS-63 Project: DdlUtils Issue Type: Bug Components: Core (No specific database) Environment: Win 2K SQL Server jtds MySQL 5.0 MySQL Connector/J Reporter: Appajee Papolu Assigned To: Thomas Dudziak Fix For: 1.0 Attachments: RowWithAsciiOneChar.txt - Dumped out a MSSQL database using ddlutils ant task - Used the resulting files to create a database in MySQL - Getting errors while importing data that have embedded XML data in their row data, for example, as in: whatever-table col1=78 col2=name col2=Set-schema: User#1;$%$#10;Query: #2; '104' LIKE quot;$GID$;%quot; OR '104' LIKE quot;%;$GID$;%quot; OR '104' LIKE quot;% $GID$;%quot;#10;Entry-list: #10;window-position: 0518 0145 0395 0326#10;end#10;/ - Receiving error as follows: [ddlToDatabase] Jan 20, 2006 7:36:58 AM org.apache.commons.digester.Digester fatalError [ddlToDatabase] SEVERE: Parse Fatal Error at line 1705 column 107: Character reference #1 is an invalid XML character. [ddlToDatabase] org.xml.sax.SAXParseException: Character reference #1 is an invalid XML character. -- 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
[jira] Resolved: (DDLUTILS-100) WriteDataToFile command not handling BLOBs correctly
[ http://issues.apache.org/jira/browse/DDLUTILS-100?page=all ] Thomas Dudziak resolved DDLUTILS-100. - Resolution: Fixed WriteDataToFile command not handling BLOBs correctly Key: DDLUTILS-100 URL: http://issues.apache.org/jira/browse/DDLUTILS-100 Project: DdlUtils Issue Type: Bug Components: Ant Tasks Environment: Win XP SP2 Java 1.5.0_06 Oracle 10g EE Reporter: Guy Davis Assigned To: Thomas Dudziak Priority: Minor Fix For: 1.0 Attachments: blob.patch We recently added a table with a BLOB column to our application. We use DDLUtils for dumping the schema and data to XML, versioning the XML files, and also loading back into clean databases. Unfortunately, the dump for the BLOB table just called toString() on the BLOB object itself which meant the BLOB data was lost. -- 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
[jira] Resolved: (DDLUTILS-40) Numeric formatting in MS SQL Server
[ http://issues.apache.org/jira/browse/DDLUTILS-40?page=all ] Thomas Dudziak resolved DDLUTILS-40. Resolution: Fixed Is applied, though I used the CAST function instead for the dates/times because this should also work with other JDBC drivers (as the driver does not evaluate the expression). Numeric formatting in MS SQL Server --- Key: DDLUTILS-40 URL: http://issues.apache.org/jira/browse/DDLUTILS-40 Project: DdlUtils Issue Type: Bug Components: Core - SqlServer Reporter: JuanFran Adame Lorite Assigned To: Thomas Dudziak Priority: Minor Fix For: 1.0 Attachments: MSSqlBuilder.java Numeric values does not have to be surrounded by quotes in SQL commands, doing so can generate errors when MS SQL Server parses a scientific format number (with quotes surrounding) to DECIMAL o NUMERIC column. -- 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
[jira] Resolved: (DDLUTILS-54) Column comparison does not check on native types
[ http://issues.apache.org/jira/browse/DDLUTILS-54?page=all ] Thomas Dudziak resolved DDLUTILS-54. Resolution: Fixed I've added a unit test for this (testIssue54 in org.apache.ddlutils.io.TestAlteration) and apparently this is already fixed. Column comparison does not check on native types Key: DDLUTILS-54 URL: http://issues.apache.org/jira/browse/DDLUTILS-54 Project: DdlUtils Issue Type: Bug Components: Core (No specific database) Reporter: Konstantinos Stathatos Assigned To: Thomas Dudziak Priority: Minor Fix For: 1.0 Attachments: derby_test.xml, svndiff, zementis_tests.ant The attached Ant script creates a table (in Derby) and then tries to alter it, using the same database description. I would expect the DdlUtils would not try to modify anything as the database has not changed. However, the database defines a BOOLEAN column and a FLOAT column which in a Derby are mapped to a SMALLINT column and a DOUBLE column. With such a mapping, next time the columns are compared DdlUtils finds them different since the type codes are different. As a result, it tries to modify the columns even though the modification is not necessary. Generally, such modification is really harmless. However, under my particular use case, occasionally a DBA would have to get involved and manually update the database if modifications are needed (i.e. if a non-empty alter sql is generated). This means that taking the extra step to check based on the native types if the modifications are material or not would be important. -- 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
[jira] Created: (DDLUTILS-128) Clean up the exceptions used in DdlUtils
Clean up the exceptions used in DdlUtils Key: DDLUTILS-128 URL: http://issues.apache.org/jira/browse/DDLUTILS-128 Project: DdlUtils Issue Type: Improvement Affects Versions: 1.0 Reporter: Thomas Dudziak Assigned To: Thomas Dudziak Fix For: 1.0 Clean up exceptions like DynaSqlException and similar ones, e.g. give them better class names etc. -- 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
[jira] Created: (DDLUTILS-129) Update to the new license header scheme
Update to the new license header scheme --- Key: DDLUTILS-129 URL: http://issues.apache.org/jira/browse/DDLUTILS-129 Project: DdlUtils Issue Type: Improvement Reporter: Thomas Dudziak Assigned To: Thomas Dudziak Priority: Critical Fix For: 1.0 -- 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
[jira] Resolved: (DDLUTILS-129) Update to the new license header scheme
[ http://issues.apache.org/jira/browse/DDLUTILS-129?page=all ] Thomas Dudziak resolved DDLUTILS-129. - Resolution: Fixed Update to the new license header scheme --- Key: DDLUTILS-129 URL: http://issues.apache.org/jira/browse/DDLUTILS-129 Project: DdlUtils Issue Type: Improvement Reporter: Thomas Dudziak Assigned To: Thomas Dudziak Priority: Critical Fix For: 1.0 -- 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
[jira] Resolved: (DDLUTILS-128) Clean up the exceptions used in DdlUtils
[ http://issues.apache.org/jira/browse/DDLUTILS-128?page=all ] Thomas Dudziak resolved DDLUTILS-128. - Resolution: Fixed Clean up the exceptions used in DdlUtils Key: DDLUTILS-128 URL: http://issues.apache.org/jira/browse/DDLUTILS-128 Project: DdlUtils Issue Type: Improvement Affects Versions: 1.0 Reporter: Thomas Dudziak Assigned To: Thomas Dudziak Fix For: 1.0 Clean up exceptions like DynaSqlException and similar ones, e.g. give them better class names etc. -- 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
[jira] Created: (DDLUTILS-130) Run unit tests on all supported databases and create doc with the results
Run unit tests on all supported databases and create doc with the results - Key: DDLUTILS-130 URL: http://issues.apache.org/jira/browse/DDLUTILS-130 Project: DdlUtils Issue Type: Task Reporter: Thomas Dudziak Assigned To: Thomas Dudziak Priority: Critical Fix For: 1.0 -- 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
[jira] Commented: (DDLUTILS-128) Clean up the exceptions used in DdlUtils
[ http://issues.apache.org/jira/browse/DDLUTILS-128?page=comments#action_12442061 ] Daniel Skiles commented on DDLUTILS-128: I retrieved the source code after these and was unable to build DdlUtils from a clean state. The DynaSqlException has changed to SqlDynaException, but not all of the calling classes have changed along with it. I've found the problem in: DynaClassCache.java DataToDatabaseSink.java AxionPlatform.java DerbyPlatform.java MckoiPlatform.java PostgreSqlPlatform.java Clean up the exceptions used in DdlUtils Key: DDLUTILS-128 URL: http://issues.apache.org/jira/browse/DDLUTILS-128 Project: DdlUtils Issue Type: Improvement Affects Versions: 1.0 Reporter: Thomas Dudziak Assigned To: Thomas Dudziak Fix For: 1.0 Clean up exceptions like DynaSqlException and similar ones, e.g. give them better class names etc. -- 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
[jira] Commented: (DDLUTILS-128) Clean up the exceptions used in DdlUtils
[ http://issues.apache.org/jira/browse/DDLUTILS-128?page=comments#action_12442075 ] Thomas Dudziak commented on DDLUTILS-128: - Yeah, I've had some trouble with subversion so not all files did get commited. This should be fixed now. Clean up the exceptions used in DdlUtils Key: DDLUTILS-128 URL: http://issues.apache.org/jira/browse/DDLUTILS-128 Project: DdlUtils Issue Type: Improvement Affects Versions: 1.0 Reporter: Thomas Dudziak Assigned To: Thomas Dudziak Fix For: 1.0 Clean up exceptions like DynaSqlException and similar ones, e.g. give them better class names etc. -- 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
[jira] Commented: (DDLUTILS-63) ddltoDatabase errors due to specific string values in table rows of data.xml -- ddltoDatabase(to MySQL) using files produced by databaseToDdl(from MSSQL)
[ http://issues.apache.org/jira/browse/DDLUTILS-63?page=comments#action_12442189 ] Appajee Papolu commented on DDLUTILS-63: [[ Old comment, sent by email on Mon, 31 Jul 2006 13:33:30 -0700 ]] Thomas, Unfortunately I am unable to locate the produced file, but I looked at the table row's specific column data using DBVisualizer and this is what I Set-schema: User$%$ Query: '104' LIKE $GID$;% OR '104' LIKE %;$GID$;% OR '104' LIKE % $GID$;% Entry-list: window-position: 0518 0145 0395 0326 end Value ends right above line As you can see, this column value indeed has embedded Ascii character 1 as a value (the square like thingy - right after User, before the $ sign). If fact this character is XML encoded out (as #1;) in the DDLUtils produced xml file - however this character does not seem to be valid is in xml char field. And hence the error while parsing this file upon import attempt. I am wondering if we can designate another type, so that export would produce different kind of XML content node for such columns (that could have non-textual ASCII characters). regards Appajee On 7/18/06, Thomas Dudziak (JIRA) [EMAIL PROTECTED] wrote: http://issues.apache.org/jira/browse/DDLUTILS-63?page=comments#action_1242203 5] - - ddltoDatabase errors due to specific string values in table rows of data.xml -- ddltoDatabase(to MySQL) using files produced by databaseToDdl(from MSSQL) -- Key: DDLUTILS-63 URL: http://issues.apache.org/jira/browse/DDLUTILS-63 Project: DdlUtils Issue Type: Bug Components: Core (No specific database) Environment: Win 2K SQL Server jtds MySQL 5.0 MySQL Connector/J Reporter: Appajee Papolu Assigned To: Thomas Dudziak Fix For: 1.0 Attachments: RowWithAsciiOneChar.txt - Dumped out a MSSQL database using ddlutils ant task - Used the resulting files to create a database in MySQL - Getting errors while importing data that have embedded XML data in their row data, for example, as in: whatever-table col1=78 col2=name col2=Set-schema: User#1;$%$#10;Query: #2; '104' LIKE quot;$GID$;%quot; OR '104' LIKE quot;%;$GID$;%quot; OR '104' LIKE quot;% $GID$;%quot;#10;Entry-list: #10;window-position: 0518 0145 0395 0326#10;end#10;/ - Receiving error as follows: [ddlToDatabase] Jan 20, 2006 7:36:58 AM org.apache.commons.digester.Digester fatalError [ddlToDatabase] SEVERE: Parse Fatal Error at line 1705 column 107: Character reference #1 is an invalid XML character. [ddlToDatabase] org.xml.sax.SAXParseException: Character reference #1 is an invalid XML character. -- 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
[jira] Commented: (DDLUTILS-61) 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-61?page=comments#action_12442190
]
Appajee Papolu commented on DDLUTILS-61:
[[ Old comment, sent by email on Mon, 31 Jul 2006 13:37:32 -0700 ]]
Thomas,
Thanks for the note. I will retry my attempt later this week and hopefully
every thing would work as I expect. Otherwise, I will let you know.
As noted in the other email, unfortunately I do not have previously produced
ddlutils data files and I do not quite remember the the specific
table/row/column that caused the following error. So I can not provide you
with the actual data in this case. But as I said if I run into any issue
later, I will definitely let you know.
Thanks again!
Appajee
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
Issue Type: Bug
Components: Core - SqlServer
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
- 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
[jira] Updated: (DDLUTILS-131) Wrong path to commons-betwixt.jar in the current maven pom
[ http://issues.apache.org/jira/browse/DDLUTILS-131?page=all ] Fredrik Westermarck updated DDLUTILS-131: - Attachment: pom.xml.patch Wrong path to commons-betwixt.jar in the current maven pom -- Key: DDLUTILS-131 URL: http://issues.apache.org/jira/browse/DDLUTILS-131 Project: DdlUtils Issue Type: Sub-task Components: Build Reporter: Fredrik Westermarck Assigned To: Thomas Dudziak Attachments: pom.xml.patch The path to the common-betwixt.jar in the lib directory were wrong so the comment on how to install the dependency dind't work. The attached patch resolves the issue. The dependency is also insalled as commons-betwixt-RC1.jar instead of commons-betwixt-dev.jar since RC1 is the version of the dependency. -- 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
[jira] Created: (DDLUTILS-133) Command-Line Invoker
Command-Line Invoker Key: DDLUTILS-133 URL: http://issues.apache.org/jira/browse/DDLUTILS-133 Project: DdlUtils Issue Type: New Feature Components: Ant Tasks Reporter: Alexander Hars Assigned To: Thomas Dudziak Priority: Minor We should be able to use DdlUtils even in non-Java, non-Ant environments. For example, I would like to use DdlUtils for running unit tests in PHP. My Php tests are not executed using Ant. It would not be very complicated to extend the tasks classes with a few CommandLine tasks. They can be modeled on the Ant tasks. Parameters could be, for example (just an initial set): cmd=(createDb | dropDb | SchemaToDb | DataToDb | DbToDtd | DataToFile | SchemaToFile | SchemaSqlToFile) driver=database driver class url=database url user=databaser user name password=database password file=file to be written to or read from .. This way, DdlUtils could be used very easily with many more programming languages and target environments. The programmer would only have to have the JRE, the DdlUtils jars (including dependencies) and the database driver installed to use DdlUtils. I am willing to do this, but need your feedback if this makes sense. -- 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
[jira] Updated: (DDLUTILS-133) Command-Line Invoker
[ http://issues.apache.org/jira/browse/DDLUTILS-133?page=all ] Thomas Dudziak updated DDLUTILS-133: Fix Version/s: 1.1 Sounds good too me ! Please check out whether you can use commons-cli (http://jakarta.apache.org/commons/cli/) to do the commandline parsing. Some suggestions: * In general, it is most useful to have the CLI in one jar file with wrapper shell script/batch files. Invocation then would be java -jar ddlutils-cli.jar ... or ddlutils ... * I would organize the commandline as follows: ddlutils main command options E.g. ddlutils createdb -cp $CLASSPATH -driver ... -username ... * For entering the password, the commandline interface should provide some interactive means (e.g. stdin). * It is quite useful to allow the specification of options via properties files. E.g. ddlutils createdb -cp $CLASSPATH -options classpath:derby.properties (loads the options file from the classpath) or ddlutils createdb -cp $CLASSPATH -options derby/derby.properties * Normal output should go to stdout (esp. if reading a schema XML from the database) unless a -output (or similar) option is used. This makes piping quite easy. * Logging should be configured to print to stderr, and have WARN as default. This can be done in code or via a log4j proeprties file embedded in the cli jar. Let me know wdyt and if you need help with this. Command-Line Invoker Key: DDLUTILS-133 URL: http://issues.apache.org/jira/browse/DDLUTILS-133 Project: DdlUtils Issue Type: New Feature Components: Ant Tasks Reporter: Alexander Hars Assigned To: Thomas Dudziak Priority: Minor Fix For: 1.1 We should be able to use DdlUtils even in non-Java, non-Ant environments. For example, I would like to use DdlUtils for running unit tests in PHP. My Php tests are not executed using Ant. It would not be very complicated to extend the tasks classes with a few CommandLine tasks. They can be modeled on the Ant tasks. Parameters could be, for example (just an initial set): cmd=(createDb | dropDb | SchemaToDb | DataToDb | DbToDtd | DataToFile | SchemaToFile | SchemaSqlToFile) driver=database driver class url=database url user=databaser user name password=database password file=file to be written to or read from .. This way, DdlUtils could be used very easily with many more programming languages and target environments. The programmer would only have to have the JRE, the DdlUtils jars (including dependencies) and the database driver installed to use DdlUtils. I am willing to do this, but need your feedback if this makes sense. -- 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
[jira] Created: (DDLUTILS-134) Bad start value when importing identity in Derby
Bad start value when importing identity in Derby Key: DDLUTILS-134 URL: http://issues.apache.org/jira/browse/DDLUTILS-134 Project: DdlUtils Issue Type: Bug Affects Versions: 1.1 Environment: PostgreSQL 8.1.4; Derby 10.2.1 Reporter: Laurent ROCHE Assigned To: Thomas Dudziak I am transfering a DB from PostgreSQL to Derby using DDL-Utils Ant program. I have columns defines as SERIAL and with data in PostgreSQL and when transfered the start value for the serial colum is ONE (in Derby) when I would expect it to be the same as in Postgres (the increment value seems strange too). -- 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
[jira] Updated: (DDLUTILS-134) Bad start value when importing identity in Derby
[ http://issues.apache.org/jira/browse/DDLUTILS-134?page=all ] Laurent ROCHE updated DDLUTILS-134: --- Attachment: test_derby.sql Here is a postgreSQL script which is an example of the table exported Bad start value when importing identity in Derby Key: DDLUTILS-134 URL: http://issues.apache.org/jira/browse/DDLUTILS-134 Project: DdlUtils Issue Type: Bug Affects Versions: 1.1 Environment: PostgreSQL 8.1.4; Derby 10.2.1 Reporter: Laurent ROCHE Assigned To: Thomas Dudziak Attachments: test_derby.sql I am transfering a DB from PostgreSQL to Derby using DDL-Utils Ant program. I have columns defines as SERIAL and with data in PostgreSQL and when transfered the start value for the serial colum is ONE (in Derby) when I would expect it to be the same as in Postgres (the increment value seems strange too). -- 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
[jira] Updated: (DDLUTILS-134) Bad start value when importing identity in Derby
[ http://issues.apache.org/jira/browse/DDLUTILS-134?page=all ] Laurent ROCHE updated DDLUTILS-134: --- Attachment: my_build.xml This is the build file used to export (from PostgreSQL) and import (into Derby). Bad start value when importing identity in Derby Key: DDLUTILS-134 URL: http://issues.apache.org/jira/browse/DDLUTILS-134 Project: DdlUtils Issue Type: Bug Affects Versions: 1.1 Environment: PostgreSQL 8.1.4; Derby 10.2.1 Reporter: Laurent ROCHE Assigned To: Thomas Dudziak Attachments: my_build.xml, test_derby.sql I am transfering a DB from PostgreSQL to Derby using DDL-Utils Ant program. I have columns defines as SERIAL and with data in PostgreSQL and when transfered the start value for the serial colum is ONE (in Derby) when I would expect it to be the same as in Postgres (the increment value seems strange too). -- 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
[jira] Updated: (DDLUTILS-134) Bad start value when importing identity in Derby
[ http://issues.apache.org/jira/browse/DDLUTILS-134?page=all ] Laurent ROCHE updated DDLUTILS-134: --- Attachment: Ddlutils-test.zip In case, somebody interested (in fixing this) does not have access to a Postgres server, here are the files produced on export (see the buil.xml file). Bad start value when importing identity in Derby Key: DDLUTILS-134 URL: http://issues.apache.org/jira/browse/DDLUTILS-134 Project: DdlUtils Issue Type: Bug Affects Versions: 1.1 Environment: PostgreSQL 8.1.4; Derby 10.2.1 Reporter: Laurent ROCHE Assigned To: Thomas Dudziak Attachments: Ddlutils-test.zip, my_build.xml, test_derby.sql I am transfering a DB from PostgreSQL to Derby using DDL-Utils Ant program. I have columns defines as SERIAL and with data in PostgreSQL and when transfered the start value for the serial colum is ONE (in Derby) when I would expect it to be the same as in Postgres (the increment value seems strange too). -- 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
