e8902a70fe
query with an ORDER BY clause. Ticket #3773 shows why that combination does not work. (CVS 6437) FossilOrigin-Name: 23f90d50737a36ebd17152dd4667948ce7049967
39 lines
948 B
Plaintext
39 lines
948 B
Plaintext
# 2009 April 2
|
|
#
|
|
# The author disclaims copyright to this source code. In place of
|
|
# a legal notice, here is a blessing:
|
|
#
|
|
# May you do good and not evil.
|
|
# May you find forgiveness for yourself and forgive others.
|
|
# May you share freely, never taking more than you give.
|
|
#
|
|
#***********************************************************************
|
|
#
|
|
# Ticket #3773: Be careful not to over-optimize when a compound
|
|
# subquery contains an ORDER BY clause.
|
|
#
|
|
#
|
|
# $Id: tkt3773.test,v 1.1 2009/04/02 16:59:47 drh Exp $
|
|
|
|
set testdir [file dirname $argv0]
|
|
source $testdir/tester.tcl
|
|
|
|
do_test tkt3773-1.1 {
|
|
db eval {
|
|
CREATE TABLE t1(a,b);
|
|
INSERT INTO t1 VALUES(2,1);
|
|
INSERT INTO t1 VALUES(33,3);
|
|
CREATE TABLE t2(x,y);
|
|
INSERT INTO t2 VALUES(123,2);
|
|
INSERT INTO t2 VALUES(4,4);
|
|
SELECT a FROM (
|
|
SELECT a, b FROM t1
|
|
UNION ALL
|
|
SELECT x, y FROM t2
|
|
ORDER BY 2
|
|
);
|
|
}
|
|
} {2 123 33 4}
|
|
|
|
finish_test
|