| Commit message (Collapse) | Author | Age |
... | |
| |
| |
| |
| |
| |
| |
| | |
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
|
| |
| |
| |
| |
| | |
version checks that OP_VerifySchema used to do.
FossilOrigin-Name: 2f3376ebf13df44e6acf27cb1f07172cd8b34033
|
| |
| |
| |
| |
| |
| |
| |
| | |
unordered because the NGQP will use those ephemeral tables to help order the
output. This is not an issue for standard SQLite since ephemeral tables
there are always ordered, regardless of the hint. It only affects systems
that substitute an alternative storage engine.
FossilOrigin-Name: f2504089df0bf4011864e67825b37f6aa3d03458
|
| |
| |
| |
| |
| | |
duplicate Select object.
FossilOrigin-Name: 5bb29b82109224a2ad02920658fabd8fb0f27b3f
|
| |
| |
| | |
FossilOrigin-Name: 87bf60637e5863c54c5e2d05aaaca0835b7aace8
|
| |
| |
| | |
FossilOrigin-Name: dea2ca6a159d5dcfd8deceedf1c2a73fb4ac1cfc
|
| |
| |
| |
| |
| | |
query as a test case.
FossilOrigin-Name: 2ad4583c0cc7988f0dfe78fd0a2eb0fdb92d835a
|
| |
| |
| |
| |
| | |
that this reference is not part of a sub-query.
FossilOrigin-Name: a296b73360d34c9364eceb2cc09a9a92adc4abb8
|
| |
| |
| |
| |
| | |
part of a recursive CTE and the sub-query is a compound query.
FossilOrigin-Name: 6bfa387e82de47ca1f40225fe28d873e29d6f481
|
| |
| |
| | |
FossilOrigin-Name: 3908e2ea2e7e5f466cbbbffdc27e0fe8dc9751ac
|
| |
| |
| |
| |
| | |
equivalent to a reference to the outermost name-context. This ensures that correlated sub-queries are correctly identified as such.
FossilOrigin-Name: 61be2da0ae623c1572819481508b044e9d32f294
|
| |
| |
| |
| |
| | |
a WITH clause) when generating code for "IN table" operators.
FossilOrigin-Name: 860aa936634a60d68e3954fc408a96a9260394e0
|
| |
| |
| | |
FossilOrigin-Name: 9472f6d820a7fb233936d9b8f7a39c9d4c4d6d73
|
| |
| |
| | |
FossilOrigin-Name: a5c2a54a07d35166911abc792008c05dea897742
|
| |
| |
| | |
FossilOrigin-Name: a26f399ba485e8127c276c5f103ec6c555e11734
|
| |
| |
| | |
FossilOrigin-Name: f461e2b3973d0fe6a7b8cb7a3aaab8a30b3e16c0
|
| |
| |
| | |
FossilOrigin-Name: 4e725f53131d3584319c710c8710a068989543c6
|
| |
| |
| | |
FossilOrigin-Name: b7e39851a75b87ebca747b26a39989560fd6362b
|
| |
| |
| |
| |
| |
| | |
multi-register OP_Copy, where possible. Fix the Synopsis comment for
multi-register OP_Copy instructions to show the correct register ranges.
FossilOrigin-Name: 2ae22dc0cbed2feca4baf89d02aaace0331971d6
|
| |
| |
| | |
FossilOrigin-Name: 4c6a659c432e4f7c0285f58675a67f967b07bb0d
|
|/
|
|
|
| |
change fixes the problem seen in the previous check-in.
FossilOrigin-Name: bfefc57554853e467ee6aeaba8d08331406fa216
|
|
|
| |
FossilOrigin-Name: 487f20366ce77f0c90865d10d5aaedd95af98694
|