make sure that the selected affinity is compatible with a literal values in
arms to the left of the arm that is used to determine affinity.
FossilOrigin-Name: bbdf22e3d989f42b963f1f2f219dfeac11db786f17ac27097ab72f72e7638a2a
after the decision of whether or not to use an index for ORDER BY has been
made.
FossilOrigin-Name: 27390051e86ad86fb35219329d359be9e83073f59782631af7fc519225e10565
subquery has an ORDER BY clause and an OFFSET, NULL out the destination
register before starting the ORDER BY so that the register will be set
correctly even if the OFFSET is larger than the number of output rows.
Fix for the problem reported in
[forum:/forumpost/0ec80f12d02acb3f|forum post 0ec80f12d02acb3f].
FossilOrigin-Name: 9282bcde301cee2a5c3c068b5b0b7ce992c155ece894413a6a9a51a81e4133fd
to select column names for VIEWs of joins so that the constructed column
names omits the underlying table names. (CVS 5386)
FossilOrigin-Name: 636cd723296a8b1709011fdd99b236ffddf3f1b0
after #2652 is fixed. The fix will be difficult and will probably take
a while. On the other hand, correlated aggregate queries have never
worked in SQLite and the problem is just now coming to light, so it is
probably not a pressing issue. (CVS 4435)
FossilOrigin-Name: 5c41619e292699c72231cff10e26dfbe9a363a00
integers. Any single non-integer input causes the result to be a floating
point value. (CVS 2669)
FossilOrigin-Name: 21adf4bd99e732650a1e8e9a1cc954126983a654
the optimizer into using a correlated subquery when a static
subquery would suffice. (CVS 2477)
FossilOrigin-Name: ef4059e3afa1a61a9e59df00cdfedc57d8df9fec
