db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Fox (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (TORQUE-251) fix SQL errors in the test project
Date Fri, 01 Feb 2013 21:34:13 GMT

     [ https://issues.apache.org/jira/browse/TORQUE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thomas Fox resolved TORQUE-251.
-------------------------------

       Resolution: Fixed
    Fix Version/s: 4.0

The test project now fails by default if the generated sql cannot be executed.
This behaviour can be changed by adding -DonSqlError=continute in the maven command line.
Checked against MySql 5.5, MSSQL 2012, Oracle 11g Express, Postgresql 9.1, Hsqldb 2.2.8 and
Derby 10.8.2.2 that the test project runs without problems.
                
> fix SQL errors in the test project
> ----------------------------------
>
>                 Key: TORQUE-251
>                 URL: https://issues.apache.org/jira/browse/TORQUE-251
>             Project: Torque
>          Issue Type: Bug
>          Components: Test Project
>            Reporter: Greg Monroe
>            Assignee: Thomas Fox
>             Fix For: 4.0
>
>
> - Running Test project against MySQL 5.1 produces errors in the
>       sql:execute phase:  Problem sql files are:
>       
>       - bookstore-schema ( ALTER TABLE / FOREIGN KEY statements)
>       - databaseMapInit-schema.sql (mostly creating date field defaults
>           and some alter table/foreign key statements )
>       - pk-schema.sql (Table exists error)
>       - test-schema.sql (ALTER TABLE / FOREIGN KEY statements)
>       - pk-schema-idtable-init.sql (Insert failed because of duplicate key)
>         
>       Note: Some of errors get hidden during second run with tables created.
>         
> - Running Test project against MS SQL 2005 produces errors in the
>       sql:execute phase.  Problem sql files are:
>       
>       - bookstore-schema.sql ( ALTER TABLE / DROP CONSTRAINT statments and
>           DROP VIEW statement)
>       - default-value-schema.sql ( mostly creating date field defaults
>           and some alter table drop constraint key statements )
>       - pk-schema.sql (Table exists error)
>       - qualified-table-name-schema.sql  (Schema exists on 2nd run)
>       - save-method-in-peer-schema.sql (ALTER TABLE / DROP CONSTRAINT stmts)
>       - test-schema.sql (ALTER TABLE/DROP CONSTRAINT and CREATE BASE table)
>       - pk-schema-idtable-init.sql (Insert failed because of duplicate key)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org


Mime
View raw message