Fix MySQL support in ERXExistsQualifier

The identifier quote character in MySLQ is the backtick (not double quote). Using double quote resulted in invalid expression. Also, by using expression.sqlStringForSchemaObjectName we respect com.webobjects.jdbcadaptor.MySQLExpression.enableIdentifierQuoting flag which is off by default in case of MySQL (resulting in no quoting at all).
wocommunity · Apr 14, 2014 · d3d496b · d3d496b · elemgee · Apr 14, 2014
1 parent 5e69b03
commit d3d496b
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/Frameworks/Core/ERExtensions/Sources/er/extensions/eof/qualifiers/ERXExistsQualifier.java b/Frameworks/Core/ERExtensions/Sources/er/extensions/eof/qualifiers/ERXExistsQualifier.java
@@ -253,7 +253,7 @@ public String sqlStringForSQLExpression(EOQualifier qualifier, EOSQLExpression e
             }
 
             EOJoin parentChildJoin = ERXArrayUtilities.firstObject(relationship.joins());
-            String destEntityForeignKey = ".\"" + parentChildJoin.destinationAttribute().columnName() + "\"";
+            String destEntityForeignKey = "." + expression.sqlStringForSchemaObjectName(parentChildJoin.destinationAttribute().columnName());
 
             EOQualifier qual = EOQualifierSQLGeneration.Support._schemaBasedQualifierWithRootEntity(subqualifier, destEntity);
             EOFetchSpecification fetchSpecification = new EOFetchSpecification(destEntity.name(), qual, null, false, true, null);