Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
Overview
| Comment: | Fix FTS3 test cases due to the flattener change of the previous check-in. |
|---|---|
| Downloads: | Tarball | ZIP archive | SQL archive |
| Timelines: | family | ancestors | descendants | both | trunk |
| Files: | files | file ages | folders |
| SHA1: |
0c8b9b211f4285e2ab77cf5e0820088e |
| User & Date: | drh 2016-09-27 00:03:25 |
Context
|
2016-09-27
| ||
| 00:09 | Update requirements marks due to improvements in the wording of documentation. No changes to code. check-in: bf903b2e user: drh tags: trunk | |
| 00:03 | Fix FTS3 test cases due to the flattener change of the previous check-in. check-in: 0c8b9b21 user: drh tags: trunk | |
|
2016-09-26
| ||
| 14:39 | When flattening a query of the form "SELECT * FROM (SELECT * FROM tbl WHERE x=?) WHERE y=?", ensure that the final WHERE clause is "x=? AND y=?" instead of "y=? AND x=?". Although it is still not guaranteed, this makes the order in which WHERE clause terms are processed comport more closely to users expectations. check-in: cf7f9e6d user: dan tags: trunk | |
Changes
Changes to test/fts3aux1.test.
113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 |
# Now show that using "term='braid'" means the virtual table returns
# only 1 row to SQLite, but "+term='braid'" means all 19 are returned.
#
do_test 2.1.2.1 {
set cnt 0
execsql { SELECT * FROM terms_v WHERE rec('cnt', term) AND term='braid' }
set cnt
} {2}
do_test 2.1.2.2 {
set cnt 0
execsql { SELECT * FROM terms_v WHERE rec('cnt', term) AND +term='braid' }
set cnt
} {38}
# Similar to the test immediately above, but using a term ("breakfast") that
# is not featured in the dataset.
#
do_test 2.1.3.1 {
set cnt 0
execsql { SELECT * FROM terms_v WHERE rec('cnt', term) AND term='breakfast' }
set cnt
} {0}
do_test 2.1.3.2 {
set cnt 0
execsql { SELECT * FROM terms_v WHERE rec('cnt', term) AND +term='breakfast' }
set cnt
} {38}
do_execsql_test 2.1.4.1 { SELECT * FROM terms_v WHERE term='braid' } {braid 1 1}
do_execsql_test 2.1.4.2 { SELECT * FROM terms_v WHERE +term='braid'} {braid 1 1}
do_execsql_test 2.1.4.3 { SELECT * FROM terms_v WHERE term='breakfast' } {}
do_execsql_test 2.1.4.4 { SELECT * FROM terms_v WHERE +term='breakfast' } {}
do_execsql_test 2.1.4.5 { SELECT * FROM terms_v WHERE term='cba' } {}
|
| | | |
113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 |
# Now show that using "term='braid'" means the virtual table returns
# only 1 row to SQLite, but "+term='braid'" means all 19 are returned.
#
do_test 2.1.2.1 {
set cnt 0
execsql { SELECT * FROM terms_v WHERE rec('cnt', term) AND term='braid' }
set cnt
} {1}
do_test 2.1.2.2 {
set cnt 0
execsql { SELECT * FROM terms_v WHERE rec('cnt', term) AND +term='braid' }
set cnt
} {19}
# Similar to the test immediately above, but using a term ("breakfast") that
# is not featured in the dataset.
#
do_test 2.1.3.1 {
set cnt 0
execsql { SELECT * FROM terms_v WHERE rec('cnt', term) AND term='breakfast' }
set cnt
} {0}
do_test 2.1.3.2 {
set cnt 0
execsql { SELECT * FROM terms_v WHERE rec('cnt', term) AND +term='breakfast' }
set cnt
} {19}
do_execsql_test 2.1.4.1 { SELECT * FROM terms_v WHERE term='braid' } {braid 1 1}
do_execsql_test 2.1.4.2 { SELECT * FROM terms_v WHERE +term='braid'} {braid 1 1}
do_execsql_test 2.1.4.3 { SELECT * FROM terms_v WHERE term='breakfast' } {}
do_execsql_test 2.1.4.4 { SELECT * FROM terms_v WHERE +term='breakfast' } {}
do_execsql_test 2.1.4.5 { SELECT * FROM terms_v WHERE term='cba' } {}
|