expressions in an aggregate query. Proposed fix for the problem identifyed by
dbsqlfuzz 8e17857db2c5a9294c975123ac807156a6559f13.
FossilOrigin-Name: 40d08807209638aad728be2cedbc904e342e76c8e486c364bd571b55dd2e1e87
clause. This brings SQLite into closer agreement with PostgreSQL and fixes
the concern raised by
[forum:/forumpost/1a7fea4651|forum post 1a7fea4651].
FossilOrigin-Name: 9322a7c21f1c22ba00e9b889223e89bc1591db6e561ce05091e905e98c1bf2b3
is stored as an INTEGER when the integer uses as much space as the real
value it proposes to stand in for (8 bytes). This avoids corner cases
of comparing integers against real values that are beyond the resolution
of an IEEE 754 double. Fix for ticket [6c1d3febc00b22d457c78c2]
FossilOrigin-Name: 9b0915272f4d4052aa31e9297424a7db9a0234b676e8e2a44c3f2dc54236705a
a REAL table column by GROUP BY. Ticket #2251. Also make sure default
values are correctly expanded. There may be other places in the code
where this issue comes up - we need to look further. (CVS 3659)
FossilOrigin-Name: e11bbf174c5a2fa75e3d1dd450c8b2a18f40e4da
of type real, though an integer representation is still sometimes used
internally for efficiency. (CVS 2753)
FossilOrigin-Name: e0d6f61c7de2c03b8fd17ef37cf1a0add36ee618
integers. Any single non-integer input causes the result to be a floating
point value. (CVS 2669)
FossilOrigin-Name: 21adf4bd99e732650a1e8e9a1cc954126983a654
side-efffect, allow the GROUP BY clause to refer to columns by their integer
column number. Ticket #237. (CVS 856)
FossilOrigin-Name: 187d9c405891e543fc706f8ddb41f3966a842214
use an index for sorting. It has to sort as a separate operation after
the GROUP BY is complete. (CVS 702)
FossilOrigin-Name: 18745c67acdf7ebec378f5538174117970e9f5cc
drh