[jira] [Commented] (TORQUE-241) qualified table names cause wrong sql to be created

["Thomas Fox (JIRA)" <ji...@apache.org>]

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

Thomas Fox commented on TORQUE-241:
-----------------------------------

Is due to fullTableAdded check fails (BasePeerImpl line 420) because not the fully qualified table name is fetched for comparison from the table map, but the unqualified name.
We need to fetch the fully qualified table name from the table map.
                
> 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