Outer join OJ syntax with JDBC drivers

Question

Hello,
I'm facing a problem with CrystalReports 2008 and jdbc connection.
Crystal genrates OJ syntax (as below) which cannot be interpreted by the Database.
SELECT "T1"."T1D", "T2"."T2D", "T3"."T3D"
FROM   {oj ("PUBLIC"."PUBLIC"."T3" "T3" LEFT OUTER JOIN "PUBLIC"."PUBLIC"."T2" "T2" ON "T3"."T2K"="T2"."T2K") LEFT OUTER JOIN "PUBLIC"."PUBLIC"."T1" "T1" ON "T2"."T1K"="T1"."T1K"}
Prensently my database is HSQLDB.
After browsing several post about ODBC, I tried to change the registry, introducing a new key
HKEY_CURRENT_USER\Software\Business Objects\Suite 12.0\Crystal Reports\DatabaseOptions\NoOuterJoinEscSeq=myodbc3,hsqldb
It did not change anything.
Now, I suppose Crystal queries the database driver for its capabilities.
This is done by a DatabaseMetaData object which implements several methods.
In case of hsqldb, here is what the driver answers:
     public boolean supportsMinimumSQLGrammar() throws SQLException {
          return false;
     public boolean supportsCoreSQLGrammar() throws SQLException {
          return true;
     public boolean supportsExtendedSQLGrammar() throws SQLException {
          return false;
     public boolean supportsANSI92EntryLevelSQL() throws SQLException {
          return false;
     public boolean supportsANSI92IntermediateSQL() throws SQLException {
          return false;
     public boolean supportsANSI92FullSQL() throws SQLException {
          return false;
     public boolean supportsIntegrityEnhancementFacility() throws SQLException {
          return true;
     public boolean supportsOuterJoins() throws SQLException {
          return true;
     public boolean supportsFullOuterJoins() throws SQLException {
          return false;
     public boolean supportsLimitedOuterJoins() throws SQLException {
          return true;
How can I tell Crystal to stop using the OJ syntax ?
Thank you and kind regards.
Alain

Answer 1

Hi Alaine,
You are correct, CR does query the driver to get what it requires to use for outer join syntax. The registry key will not work for this driver. It's the driver meta layer telling CR to use the oj syntax and is dependent on the driver being configured.
Not sure if you can but start by trying to alter these settings if you can:
public boolean supportsOuterJoins() throws SQLException {
return true;
public boolean supportsFullOuterJoins() throws SQLException {
return false;
I would think both should be reversed, true to false and false to true.
Before you do that though go to our download page and install Service Pack 2, it may by a CR issue and the patch may have fixed the problem.
If it doesn't I suggest asking this on the HSQLDB forum to see how to alter those option. CR follows the JDBC Type 4 Standards. You may want to see if Sun has a HSQLDB JDBC driver also.
Thank you
Don