diff options
| author | drh <> | 2021-07-22 16:07:01 +0000 |
|---|---|---|
| committer | drh <> | 2021-07-22 16:07:01 +0000 |
| commit | 348e002ec90494809e8151e3738157edf5483ff6 (patch) | |
| tree | f743cda9c0af55bf1588e3c7343fdc28e5ba7894 /src/treeview.c | |
| parent | c8d214711f39045a079c7ee9aa33b933e3a037a7 (diff) | |
| download | sqlite-348e002ec90494809e8151e3738157edf5483ff6.tar.gz sqlite-348e002ec90494809e8151e3738157edf5483ff6.zip | |
One of the optimizations of check-in [de9c86c9e4cdb34f] does not work for
terms originating in the ON/USING clause, as demonstrated by
[forum:/forumpost/6cf3bb457c3f4685|forum post 6cf3bb457c3f4685]. This
check-in disables that optimization for ON/USING terms. Also improve the
TreeView display for the resulting "true"/"false" nodes to show that they
originate from the ON/USING clause. Add a testcase() to the other optimization
to show that it can still be used for ON/USING terms.
FossilOrigin-Name: 1f6796044008e6f3a61bcf390c0c7eb31947e971f0edada74e7a3a211f8ae76a
Diffstat (limited to 'src/treeview.c')
| -rw-r--r-- | src/treeview.c | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/src/treeview.c b/src/treeview.c index 165ceb537..654e01a3e 100644 --- a/src/treeview.c +++ b/src/treeview.c @@ -474,8 +474,8 @@ void sqlite3TreeViewExpr(TreeView *pView, const Expr *pExpr, u8 moreToFollow){ break; } case TK_TRUEFALSE: { - sqlite3TreeViewLine(pView, - sqlite3ExprTruthValue(pExpr) ? "TRUE" : "FALSE"); + sqlite3TreeViewLine(pView,"%s%s", + sqlite3ExprTruthValue(pExpr) ? "TRUE" : "FALSE", zFlgs); break; } #ifndef SQLITE_OMIT_BLOB_LITERAL |