| Commit message (Collapse) | Author | Age |
|
|
| |
FossilOrigin-Name: 8d27e3e16a9be79fe227e833f4770ebe09a9d90b
|
|
|
|
|
| |
under some circumstances.
FossilOrigin-Name: eddc05e7bb31fae74daa86e0504a3478b99fa0f2
|
|\
| |
| |
| |
| |
| |
| | |
And do not flatten an aggregate subquery into a query that uses other
subqueries. Fixes for tickets [ca0d20b6cdddec5] and
[2f7170d73bf9], respectively.
FossilOrigin-Name: 24e78b8d65734a6a8ae21a20542cd1839e756fb1
|
| |
| |
| |
| |
| | |
Initial fix for ticket [ca0d20b6cdddec5e8].
FossilOrigin-Name: c053448a55f9d030e8ffe88cf4fc14ada7f6ec19
|
|/
|
|
|
|
|
| |
uses other subqueries in its result set or WHERE clause or ORDER BY clause.
Preliminary fix for ticket [2f7170d73bf9abf8]. However it still contains
a defect similar to the COLLATE problem of [ca0d20b6cddd].
FossilOrigin-Name: 0b7d65e3fda676d193347cb782854c28a48252af
|
|
|
| |
FossilOrigin-Name: 4ef7ceced2b0000d21f7f8014384c04a0e4661d3
|
|
|
|
|
|
|
| |
that comes about because the Expr.pTab field is checked on an
EXPR_REDUCEDSIZE Expr object before checking the Expr.op field to
know that the Expr.pTab field is meaningless.
FossilOrigin-Name: e098de691002a78270540430b0df1e120582b53f
|
|
|
| |
FossilOrigin-Name: 5f592359d6d41708da3b3ac9d987a1631bfa3d88
|
|
|
|
|
| |
Ticket [a59ae93ee990a55].
FossilOrigin-Name: fe5788633131281a0f27c5b75993ce2ff958bfeb
|
|
|
|
|
|
| |
table can be NULL even if that column as a NOT NULL constraint.
Fix for ticket [6f2222d550f5b0ee7ed].
FossilOrigin-Name: 6f6fcbe4736b9468a495c684d5eebc8bfe5c566a
|
|
|
|
|
| |
No changes to code.
FossilOrigin-Name: 6d00bcca6ed1903fb17275752cab71c14392355b
|
|
|
|
|
| |
...)" expressions. Fix for [db87229497].
FossilOrigin-Name: 55e453aadbb676dda07f0fa537d39ce184ef636c
|
|
|
|
|
| |
doing so gives the same answer for less work.
FossilOrigin-Name: d95d0313c447f5baeabdb17284d8606331ab7d49
|
|
|
|
|
| |
No changes to production code.
FossilOrigin-Name: 07c89940c49a5dca3205a4b6fa8290f23bcb6e10
|
|
|
|
|
|
| |
debugging display routines: sqlite3TreeViewExpr(), sqlite3TreeViewExprList(),
and sqlite3TreeViewSelect().
FossilOrigin-Name: 4ff51325d6b41d0c59e303b573700ec80c51d216
|
|
|
|
|
| |
Ticket [78c0c8c3c9f7c1].
FossilOrigin-Name: 1ad2bc1ed4c4ac81ac67a9660761f0eeb47c7fef
|
|
|
| |
FossilOrigin-Name: c0b61f7092a7fd2c5f51db26ce7a7a5c75c227fe
|
|
|
|
|
| |
testfixture. Add new SELECTTRACE() calls.
FossilOrigin-Name: f1ba68f131d2f03e4a7bc50cde23a7609d384279
|
|
|
| |
FossilOrigin-Name: 320556233e19cdd9d590a09655c3465754700d39
|
|
|
| |
FossilOrigin-Name: e62aab5e9290503869e1f4d5e0fefd2b4dee0a69
|
|
|
| |
FossilOrigin-Name: 462f42af52f146fd328ddcbbe78c8444ef7bd2c3
|
|
|
|
|
|
|
| |
argument of an ALTER TABLE ADD COLUMN and to be understand on the RHS of
range constraints interpreted by STAT3/4. This involves a rewrite of the
implementation of the CAST operator.
FossilOrigin-Name: 91d8a8d0b792ea5c4fe68fd9caaf3345eddea486
|
|
|
|
|
|
|
| |
The error message is not quite as good, but as this error has apparently
not previously occurred in over 8 years of heavy use, that is not seen as
a serious problem.
FossilOrigin-Name: 0ad1ed8ef0b5fb5d8db44479373b2b93d8fcfd66
|
|
|
|
|
|
| |
value for a table column.
Candidate fix for ticket [3a88d85f36704eebe134f7].
FossilOrigin-Name: 29ba812825bf06ef230f2480bba0579653f0a52d
|
|
|
|
|
| |
VDBE code.
FossilOrigin-Name: 01f60027ad1841051fa493a646141445f8971357
|
|
|
| |
FossilOrigin-Name: 7fdf26da1d2f40b80f9e44ff6f5af22ace8f95f3
|
|
|
| |
FossilOrigin-Name: 92ba2821468ecbfac2469161d81c873de67b2243
|
|
|
|
|
|
| |
faster queries in some cases, for example when the RHS of the IN operator
changes for each row of a large table scan.
FossilOrigin-Name: 436e884215e2b33ca3fbb555362237b12827c07a
|
|
|
|
|
| |
logic.
FossilOrigin-Name: 9bc1c730a366e75b760b58e7a343d39165b2a469
|
|
|
| |
FossilOrigin-Name: 468e730036edac22cfeb9ea3515aa16e6bcd6650
|
|
|
|
|
|
| |
comments explaining the IN-operator code, though it is not clear that the
comments are correct even yet - more work to be done.
FossilOrigin-Name: c11e55fabbc718cb324ecd3540453c25db98f50c
|
|
|
|
|
|
|
| |
turns out to be helpful. If the list is of length 1 or 2, the OR expression
is very slightly faster, but the ephemeral table approach is clearly better for
all list lengths greater than 2. Better to keep the code simple.
FossilOrigin-Name: e13175d3579e1045165bab091b3b28951d691704
|
|
|
|
|
| |
and to make the code easier to understand.
FossilOrigin-Name: ee0fd6aaf94cda1dce3fe752bfe3b0f83e0043f1
|
|
|
|
|
| |
"IsUniqueIndex(pIndex)". Easier to understand that way.
FossilOrigin-Name: e75b26ee357bb3d3c1a539b05d633ebf314726d7
|
|
|
|
|
| |
where the LHS is a rowid.
FossilOrigin-Name: 1361450a9dfe9476e8df98f370a3695752252245
|
|
|
|
|
|
| |
since it should not make any difference in the output but dues consume extra
memory and CPU time.
FossilOrigin-Name: f4cb53651b1e352fae7378878b830a902bcd9248
|
|
|
|
|
| |
hex integers are omitted at compile time.
FossilOrigin-Name: a5b383e077e4b277a65920f7cc202f32f07aa9ee
|
|
|
|
|
|
|
| |
hex literals. Casting and coercing string literals into numeric values does
not understand hexadecimal integers. This preserves backwards compatibility.
Also: Throw an error on any hex literal that is too big to fit into 64 bits.
FossilOrigin-Name: 6c6f0de59bf96b79c8ace8c9bfe48c7a6a306a50
|
|
|
|
|
| |
[9a8b09f8e6].
FossilOrigin-Name: 92f7ad43dbfe4e02490df2f932c3c74fb89064d6
|
|
|
|
|
| |
ALWAYS() on an always-true conditional in sqlite3VdbeResolveLabel().
FossilOrigin-Name: ab23abf392175d3e256ff619b13abbbe732a49ed
|
|\
| |
| | |
FossilOrigin-Name: eca35871c34374ca9189c7c9b6d490ac3c30357f
|
| |
| |
| |
| |
| | |
Add an ALWAYS() around a conditional in the parser that cannot be false.
FossilOrigin-Name: d5a1530bdc7ace053d05d1a037551110021d3758
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
incorrect, as demonstrated by the in4-5.1 test case in this check-in.
The "COLLATE binary" that was being added to the RHS of IN was overriding
the implicit collating sequence of the LHS. This change defines the EP_Generic
expression node property that blocks all affinity or collating sequence
information in the expression subtree and adds that property to the expression
taken from RHS of the IN operator.
FossilOrigin-Name: 2ea4a9f75f46eaa928ba17e9e91bc0432750d46d
|
| |
| |
| | |
FossilOrigin-Name: b1435f26b07b2208cfcca557f96342a5bd0d5328
|
|/
|
|
|
| |
There are many problems still to be worked out.
FossilOrigin-Name: 59742dd4c5259883850044d0938248b009ebd045
|
|
|
|
|
| |
testing.
FossilOrigin-Name: b92d31a97d5fe4606d9ae1393c7f3e052f46bf5a
|
|
|
|
|
|
|
|
| |
on the RHS on the first iteration, then remember the result. There has been
logic to do this for year, but it didn't work right and ended up repeating
the NULL test on every iteration. This inefficiency was found using the
VDBE coverage testing tools.
FossilOrigin-Name: 915f6f1c7aab54583729e60bdc1565f25ecc6f74
|
|
|
| |
FossilOrigin-Name: ce184c7bb16988641d37c908d9b3042456d4be3d
|
|
|
|
|
|
| |
generates output directly in the registers that INSERT INTO will be using,
in many cases, and OP_SCopy operations can thus be avoided.
FossilOrigin-Name: aa2d8b0e8154dd2f5e2c837dc11ab362b083495b
|
|
|
|
|
| |
of a compound query. Proposed fix for ticket [31a19d11b97088296a].
FossilOrigin-Name: 67bfd59d9087a987f15f6148efa1ff104983e1fb
|