[
https://issues.apache.org/jira/browse/TORQUE-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13490308#comment-13490308
]
Thomas Fox commented on TORQUE-241:
-----------------------------------
Other errors with schemata:
- in idtable-init.sql the fully qualified name of the table is used, causing
the idbroker not to find the table's entry
- in some databases, the schema must be created explicitly by the "create
schema" command
- the qualified table name was used in the peer's TABLE_NAME constant
> 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: [email protected]
For additional commands, e-mail: [email protected]
