db-torque-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ralph Weires (JIRA)" <j...@apache.org>
Subject [jira] Issue Comment Edited: (TORQUE-108) Criteria addJoin causes incorrect SQL to be generated when optional schema references are in use (Oracle)
Date Mon, 29 Sep 2008 07:08:44 GMT

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

rweires edited comment on TORQUE-108 at 9/29/08 12:07 AM:
---------------------------------------------------------------

I have the exact same problem using a MSSQL database with a custom schema (instead of the
default 'dbo' schema). The SQL generated for queries without joins works fine, but as soon
as I add a join (addJoin), the generated SQL becomes invalid, in the same way as already described
by Brendan above.

I checked the latest SVN trunk and saw that the patch provided by Brendan is not included
there yet, so is there a chance this patch might become integrated anytime soon?

      was (Author: rweires):
    I have the exact same problem using a MSSQL database with a custom schema (instead of
the default 'dbo' schema). The SQL generated for queries without joins works fine, but as
soon as I add a join (doJoin), the generated SQL becomes invalid, in the same way as already
described by Brendan above.

I checked the latest SVN trunk and saw that the patch provided by Brendan is not included
there yet, so is there a chance this patch might become integrated anytime soon?
  
> Criteria addJoin causes incorrect SQL to be generated when optional schema references
are in use (Oracle)
> ---------------------------------------------------------------------------------------------------------
>
>                 Key: TORQUE-108
>                 URL: https://issues.apache.org/jira/browse/TORQUE-108
>             Project: Torque
>          Issue Type: Bug
>          Components: Runtime
>    Affects Versions: 3.3-RC1, 3.3-RC2, 3.3-RC3
>         Environment: Linux, Java 1.6
>            Reporter: Brendan Miller
>         Attachments: joinbuilder.patch, JoinBuilderTest.java
>
>
> I previously wrote about this to torque-user in Oct 2007.
> In a schema definition that includes torque.dsfactory.programs.schema, writing the following
> Criteria crit = new Criteria();
> crit.addJoin(TransactionPeer.ORDER_ID, OrderPeer.ID);
> crit.add(TransactionPeer.ACCT_ID, account.getID());
> List<Order> orders = OrderPeer.doSelect(crit);
> generates
> SELECT <..ORDERS columns..> FROM TRANSACTION, ORDERS, DBSCHEMA.ORDERS, DBSCHEMA.TRANSACTION
> WHERE TRANSACTION.ORDER_ID=ORDERS.ID AND TRANSACTION.ACCT_ID= ?
> Upon examining the Torque code, it appears that SQLBuilder.processJoins does not add
the full table names, while SQLBuilder.processCriterions does.
> Shouldn't they both add the full table names?

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
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