[jira] Commented: (CAY-1114) EJBQLQuery fails on joins outside of public schema

From: Andrus Adamchik (JIRA) ("Andrus)
Date: Wed Oct 01 2008 - 16:00:11 EDT

  • Next message: Andrus Adamchik (JIRA): "[jira] Commented: (CAY-1114) EJBQLQuery fails on joins outside of public schema"

        [ https://issues.apache.org/cayenne/browse/CAY-1114?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13131#action_13131 ]

    Andrus Adamchik commented on CAY-1114:
    --------------------------------------

    Oops, scratch that. You alreadt did :-) Thanks!

    > EJBQLQuery fails on joins outside of public schema
    > --------------------------------------------------
    >
    > Key: CAY-1114
    > URL: https://issues.apache.org/cayenne/browse/CAY-1114
    > Project: Cayenne
    > Issue Type: Bug
    > Components: Cayenne Core Library
    > Affects Versions: 3.0
    > Reporter: Dave Dombrosky
    > Assignee: Andrus Adamchik
    > Attachments: fixEJBQLTableAlias.patch
    >
    >
    > I noticed that my EJBQL queries were failing because of incorrect table aliases. I did some troubleshooting and found out that the key for the table alias would sometimes be different depending on which translator/appender was running.
    > The problem turned out to be getting the name from the DBEntity. In some places it was just getting the regular name (DbEntity.getName()) while in other places, it was getting the full name (DbEntity.getFullyQualifiedName()). This is only a problem when you have a table in a schema other than public, because for the public schema the two method calls return the same value.
    > Changing the calls to EJBQLTranslationContext.getTableAlias() to always use the fully qualified name seems to have fixed my issues. 

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

    This archive was generated by hypermail 2.0.0 : Wed Oct 01 2008 - 16:00:33 EDT