Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix a typo in a test script on this branch. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | left-join-omit-fix |
| Files: | files | file ages | folders |
| SHA3-256: |
bff5dcfd2b29ee4834258914410a5dee |
| User & Date: | dan 2017-11-20 15:45:03 |
Context
|
2017-11-20
| ||
| 15:46 | Fix a problem preventing the planner from identifying scans that visit at most one row in cases where that property is guaranteed by a unique, not-null, non-IPK column that is the leftmost in its table. (check-in: 7fdb1e2a user: dan tags: trunk) | |
| 15:45 | Fix a typo in a test script on this branch. (Closed-Leaf check-in: bff5dcfd user: dan tags: left-join-omit-fix) | |
| 14:40 | Fix a problem preventing the planner from identifying scans that visit at most one row in cases where that property is guaranteed by a unique, not-null, non-IPK column that is the leftmost in its table. (check-in: 299d7ca5 user: dan tags: left-join-omit-fix) | |
Changes
Changes to test/join2.test.
98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 |
# that makes this possible happens to be the leftmost in its table.
#
reset_db
do_execsql_test 3.0 {
CREATE TABLE t1(k1 INTEGER PRIMARY KEY, k2, k3);
CREATE TABLE t2(k2 INTEGER PRIMARY KEY, v2);
# Prior to this problem being fixed, table t3_2 would be omitted from
# the join queries below, but if t3_1 were used in its place it would
# not.
CREATE TABLE t3_1(k3 PRIMARY KEY, v3) WITHOUT ROWID;
CREATE TABLE t3_2(v3, k3 PRIMARY KEY) WITHOUT ROWID;
}
do_eqp_test 3.1 {
SELECT v2 FROM t1 LEFT JOIN t2 USING (k2) LEFT JOIN t3_1 USING (k3);
} {
|
| | | |
98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 |
# that makes this possible happens to be the leftmost in its table.
#
reset_db
do_execsql_test 3.0 {
CREATE TABLE t1(k1 INTEGER PRIMARY KEY, k2, k3);
CREATE TABLE t2(k2 INTEGER PRIMARY KEY, v2);
-- Prior to this problem being fixed, table t3_2 would be omitted from
-- the join queries below, but if t3_1 were used in its place it would
-- not.
CREATE TABLE t3_1(k3 PRIMARY KEY, v3) WITHOUT ROWID;
CREATE TABLE t3_2(v3, k3 PRIMARY KEY) WITHOUT ROWID;
}
do_eqp_test 3.1 {
SELECT v2 FROM t1 LEFT JOIN t2 USING (k2) LEFT JOIN t3_1 USING (k3);
} {
|