db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ma...@apache.org
Subject svn commit: r546002 - /db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/SetOperatorNode.java
Date Mon, 11 Jun 2007 04:44:26 GMT
Author: mamta
Date: Sun Jun 10 21:44:25 2007
New Revision: 546002

URL: http://svn.apache.org/viewvc?view=rev&rev=546002
Log:
DERBY-2777
SetOperatorNode was using current compilation schema's collation if there is a parameter involved.
Instead, let the parameter pick up it's
collation from it's context.


Modified:
    db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/SetOperatorNode.java

Modified: db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/SetOperatorNode.java
URL: http://svn.apache.org/viewvc/db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/SetOperatorNode.java?view=diff&rev=546002&r1=546001&r2=546002
==============================================================================
--- db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/SetOperatorNode.java
(original)
+++ db/derby/code/trunk/java/engine/org/apache/derby/impl/sql/compile/SetOperatorNode.java
Sun Jun 10 21:44:25 2007
@@ -728,9 +728,6 @@
 				** type array.
 				*/
 				rc.getExpression().setType(types[index]);
-				//collation of ? operand should be same as the compilation schema
-				rc.getExpression().setCollationUsingCompilationSchema(
-						StringDataValue.COLLATION_DERIVATION_IMPLICIT);
 			}
 		}
 	}



Mime
View raw message