Generated SQL does not have fully qualified columnnames

Question

Hi,
I'm trying to run a JDO query which results in:
[code=-5001, state=42703]
java.sql.SQLException: [SQL5001] Column qualifier or table CUSTOMER
undefined.
The model is basically like this:
Class Order has a 1-1 relation with Class CustomerRole which in turn has a
n-1 relation with Class Customer
Class Order and CustomerRole are both mapped to table SCHEMA1.ORDER (the
ORDER table contains the FK to the CUSTOMER table)
Class Customer is mapped to table SCHEMA2.CUSTOMER
I perform a query using an Extend of class Order.
I add the following filter to the query:
"this.CustomerRole.Customer != null"
(CustomerRole is the name of the relation between Order and CustomerRole,
while Customer is the name of the relation between CustomerRole and
Customer)
When I execute this query, I get the following message:
kodo.util.DataStoreException: [SQL5001] Column qualifier or table CUSTOMER
undefined. {SELECT t0.ID, t2.CUSTID, t3.ADDRESS, t4.COUNTRY,
t4.COUNTRYNAME, t2.NAME FROM SCHEMA1.ORDER t0 INNER JOIN SCHEMA1.ORDER t1
ON t0.ID = t1.ID LEFT OUTER JOIN SCHEMA2.CUSTOMER t2 ON t1.CUSTID =
t2.CUSTID LEFT OUTER JOIN SCHEMA2.CUSTOMER t3 ON t2.CUSTID = t3.CUSTID
LEFT OUTER JOIN SCHEMA1.COUNTRY t4 ON t3.COUNTRY = t4.COUNTRY WHERE (0 <
(SELECT COUNT(*) FROM SCHEMA2.CUSTOMER WHERE CUSTOMER.CUSTID =
t1.CUSTID))} [code=-5001, state=42703]
NestedThrowables:
com.solarmetric.jdbc.ReportingSQLException: [SQL5001] Column qualifier or
table CUSTOMER undefined. {SELECT t0.ID, t2.CUSTID, t3.ADDRESS,
t4.COUNTRY, t4.COUNTRYNAME, t2.NAME FROM SCHEMA1.ORDER t0 INNER JOIN
SCHEMA1.ORDER t1 ON t0.ID = t1.ID LEFT OUTER JOIN SCHEMA2.CUSTOMER t2 ON
t1.CUSTID = t2.CUSTID LEFT OUTER JOIN SCHEMA2.CUSTOMER t3 ON t2.CUSTID =
t3.CUSTID LEFT OUTER JOIN SCHEMA1.COUNTRY t4 ON t3.COUNTRY = t4.COUNTRY
WHERE (0 < (SELECT COUNT(*) FROM SCHEMA2.CUSTOMER WHERE CUSTOMER.CUSTID =
t1.CUSTID))} [code=-5001, state=42703]
java.sql.SQLException: [SQL5001] Column qualifier or table CUSTOMER
undefined.
     at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:63)
     at kodo.jdbc.sql.SQLExceptions.getDataStore(SQLExceptions.java:51)
     at
kodo.jdbc.runtime.AbstractSelectResultObjectProvider.handleCheckedException(AbstractSelectResultObjectProvider.java:150)
     at com.solarmetric.rop.WindowResultList.<init>(WindowResultList.java:57)
     at
kodo.jdbc.runtime.JDBCFetchConfigurationImpl.newResultList(JDBCFetchConfigurationImpl.java:135)
     at
kodo.runtime.CopyOnWriteFetchConfiguration.newResultList(CopyOnWriteFetchConfiguration.java:159)
     at kodo.query.AbstractQuery.executeWithMap(AbstractQuery.java:750)
     at kodo.query.AbstractQuery.execute(AbstractQuery.java:633)
     at TestApp.<init>(TestApp.java:67)
     at TestApp.main(TestApp.java:135)
The problem is the last part of the query where it selects from
SCHEMA2.CUSTOMER while the Where part refers to just CUSTOMER (without
schema qualifier).
Are there any ideas to solve this? Is there a way to force columnnames
always being fully qualified in generated SQL statements?
Thanks,
Regards,
Alexander

Answer 1

Unfortunately, this is a bug that has to be fixed on our end. We'll
make sure a fix is in the next 3.1 release. Thanks for the report!