distinguishing between "subquery" and "join" and using consistent names
across EQP and bytecode.
FossilOrigin-Name: a2d3ee92420ec564e31eb0005367cf7ff3d00bfaed5a98ffdbe17c91c95d9d97
to end with OP_Copy but is not a candidate for the optimization due to jumps,
then the optimization is correctly bypassed.
FossilOrigin-Name: b36126c1889e323c9a8f04b4f4884576993c845e7d393e5e73aaa6ab5158c1f9
generate the code out of the copy, in case the code generator makes
modifications to expression and the Select object needs to be reused.
FossilOrigin-Name: 4edddcc0bc8d71e9b8abac67bc3766f1d9143dddd1f59264859ce65e5aa9b8c6
INSERT statement. The same assert() appears again in the VDBE and will fire
there if the problem persists in an SQL statement that does not contain
errors. Gramfuzz find.
FossilOrigin-Name: 9bdd57cb9ad8ac1f4a0f1a3942d94ca5193109eeb1975343c4f0c7abf7135946
very last token in the SQL statement. This fixes a problem introduced
by check-in [0fdf97efe5df745510c6b] and reported by the community during
beta-testing.
FossilOrigin-Name: 36b89d728ff13d395fe0e1db8e7c01263f73dccb278b3ece27f6ef78e909b492
expressions. Change Expr.zToken to Expr.u.zToken and added Expr.u.iValue.
Remove an unnecessary ExprDup from CHECK constraint processing. And so forth. (CVS 6682)
FossilOrigin-Name: 4ac2bdfbb4230b6ceaae87e738fa61036bbe03cb
Expr.token into a char* Expr.zToken. Also simplify the Token object by
removing the Token.dyn and Token.quoted fields. (CVS 6681)
FossilOrigin-Name: 7cb1c3ba0759539cb035978fdaff6316775986f3
to select column names for VIEWs of joins so that the constructed column
names omits the underlying table names. (CVS 5386)
FossilOrigin-Name: 636cd723296a8b1709011fdd99b236ffddf3f1b0
Other bug fixes in compound-merge. The compound-merge is still disabled
in this check-in using "#if 0" due to additional bugs. (CVS 5295)
FossilOrigin-Name: 95037e6dbf4ed0ffd38790f3270dcaa4c1ae64ed
But there are still a few problems and so the optimization is disabled by
and "#if 0". This check-in is to synchronize with the other changes happening
in parallel. (CVS 5291)
FossilOrigin-Name: e2ba324cbcac0ba35bbde50048677e085abb092b
solution for ticket #2822. Needs more testing and documentation
before going final. (CVS 4602)
FossilOrigin-Name: 62a78d212c53a9cb1759d03134653a75f3a086b6
this works for subqueries, especially in the right-hand side of an IN
operator. Ticket #2296. (CVS 3842)
FossilOrigin-Name: cfc6f933dc60ca88ae848f7f0c402e820437c2ff
the left-most select. This makes SQLite work like other SQL database,
but it also is a change from historical behavior and may break some
scripts. Ticket #1721. (CVS 3153)
FossilOrigin-Name: 80cda9f7ce83f2de6cd2fdaf6150bbc35b670fee
the execsql tcl command so that the select1 test works with the serialized
statement extension. (CVS 3136)
FossilOrigin-Name: 4d70013a6a42a58bc7af3a87bf79c131a0070e96
and a floating point result is returned for approximate results.
Tickets #1664, #1669, and #1670. (CVS 3066)
FossilOrigin-Name: 9e04f8fdf1ec0dc36effb55c05d075b3b4777fef
integers. Any single non-integer input causes the result to be a floating
point value. (CVS 2669)
FossilOrigin-Name: 21adf4bd99e732650a1e8e9a1cc954126983a654
source column without the "table." prefix. In other words,
"PRAGMA short_column_names=ON" is now the default.
This makes the names of columns behave more like other SQL engines.
The old behavior can be restored by setting "PRAGMA short_column_names=OFF". (CVS 2231)
FossilOrigin-Name: 9295050af1bf2d9d4dc63adc225a2848d67cbe17
