You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-commits@db.apache.org by ma...@apache.org on 2009/06/10 06:16:17 UTC

svn propchange: r783168 - svn:log

Author: mamta
Revision: 783168
Modified property: svn:log

Modified: svn:log at Wed Jun 10 04:16:17 2009
------------------------------------------------------------------------------
--- svn:log (original)
+++ svn:log Wed Jun 10 04:16:17 2009
@@ -1,4 +1,4 @@
-Following is the patch description. 
+Following is the patch description for DERBY-3926. 
 The problem with the trunk codeline is that when optimizer goes through optimizables in a join order, it only looks at those optimizables individually to decide whether sorting can be avoided on them or not. That approach leaves out few queries which require sorting but do not get sorted. The decision for avoiding sorting should also include relationship between the optimizables in a given join order. Following query demonstrates the trunk problem 
 SELECT table1.id, table2.value, table3.value FROM --DERBY-PROPERTIES joinOrder=FIXED 
 table3 -- DERBY-PROPERTIES index=nonUniqueOnValue_Table3