You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by "Dave Dombrosky (JIRA)" <ji...@apache.org> on 2010/02/11 06:52:28 UTC

[jira] Updated: (CAY-1376) Certain EJBQL queries have mismatched table aliases

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

Dave Dombrosky updated CAY-1376:
--------------------------------

    Attachment: testGroupByChainedJoins.patch

Added attachment that shows the problem.  Looks like the tables don't need to be in different schemas, which would explain why the getTablesAlias() fixes didn't resolve the issue.

> Certain EJBQL queries have mismatched table aliases
> ---------------------------------------------------
>
>                 Key: CAY-1376
>                 URL: https://issues.apache.org/jira/browse/CAY-1376
>             Project: Cayenne
>          Issue Type: Bug
>          Components: Core Library
>    Affects Versions: 3.0RC2
>            Reporter: Dave Dombrosky
>             Fix For: 3.0RC2
>
>         Attachments: ejbqlGroupBy.patch, jointEntityNamesGenerationFix-mismatchedAliases.patch, testGroupByChainedJoins.patch
>
>
> On some EJBQL queries, the wrong table aliases are being use to refer to columns.  A similar issue was solved earlier in CAY-1114.  This problem seems to occur when EJBQLTranslationContext.getTableAlias() is called on relationships that span database schemas.

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