[CAY-1114] EJBQLQuery fails on joins outside of public schema

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.0
• Fix Version/s: 3.0M5
• Component/s: Core Library
• Assignee: Andrus Adamchik
• Reporter: Dave Dombrosky
• Created: 01/Oct/08 19:47
• Updated: 08/Nov/08 22:32
• Resolved: 01/Oct/08 20:05

Description

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.