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] [Commented] (TORQUE-241) qualified table names cause wrong sql to be created
Date Tue, 30 Oct 2012 21:54:11 GMT

    [ https://issues.apache.org/jira/browse/TORQUE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487282#comment-13487282

Thomas Fox commented on TORQUE-241:

Derby does not resolve unqualified table names in select columns to fully qualified table
names. In other words, the query
delete from bookstore.book where book.id=1
dies not work, derby needs
delete from bookstore.book where bookstore.book.id=1
Mysql and postgresql accept both variants.
Need to check with mssql, hsqldb and oracle.
> qualified table names cause wrong sql to be created
> ---------------------------------------------------
>                 Key: TORQUE-241
>                 URL: https://issues.apache.org/jira/browse/TORQUE-241
>             Project: Torque
>          Issue Type: Bug
>          Components: Runtime
>    Affects Versions: 4.0-beta1
>            Reporter: Thomas Fox
> If I use the table name "bookstore.book" and then try to telete all booksby
>         Criteria criteria = new Criteria();
>         criteria.where(BookPeer.BOOK_ID, (Long) null, Criteria.NOT_EQUAL);
>         BookPeer.doDelete(criteria);
>  the generated sql will be
> DELETE FROM bookstore.book, book WHERE book.book_id IS NOT NULL
> whereas it should be
> DELETE FROM bookstore.book WHERE book.book_id IS NOT NULL
> Also other places should be checked for similar errors.

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

View raw message