Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
History for test/select4.test
|
2025-04-10
| ||
| 10:18 | [21941409ac] part of check-in [20acd630b9] Remove unnecessary "www." prefixes on domain names in URLs. (check-in: [20acd630b9] user: drh branch: trunk, size: 26858) | |
|
2023-06-09
| ||
| 13:08 | [b5b57fb83d] part of check-in [f587891134] Experimental change to add a per-connection option that raises an error if a bare column appears in an aggregate query. (check-in: [f587891134] user: drh branch: newbie-safe-aggregates, size: 26949) | |
|
2021-03-31
| ||
| 13:31 | [f0684d3da3] part of check-in [c36b43589a] Defer deletion of expressions that are optimized out by the AND optimizer in the sqlite3ExprAnd() routine until the corresponding Parse object is deleted. This avoids a dangling pointer in AggInfo if sqlite3ExprAnd() is invoked by the push-down optimization. The dangling pointer appears to be harmless in release builds, only showing up in debug builds. Problem found by dbsqlfuzz. (check-in: [c36b43589a] user: drh branch: trunk, size: 26866) | |
|
2020-04-04
| ||
| 00:15 | [e8a2502e36] part of check-in [70c44811d1] In the push-down optimization, do not substitute columns that have previously been identified as being constant by the propagate-constants optimization. Fix for ticket [51166be0159fd2ce] (check-in: [70c44811d1] user: drh branch: trunk, size: 26150) | |
|
2017-07-17
| ||
| 19:25 | [ddcaffe162] part of check-in [adc082c146] When checking for the WHERE-clause push-down optimization, verify that all terms of the compound inner SELECT are non-aggregate, not just the last term. Fix for ticket [f7f8c97e97597]. (check-in: [adc082c146] user: drh branch: push-down-backport, size: 22240) | |
|
2016-04-25
| ||
| 02:20 | [5389d98959] part of check-in [ec215f94ac] When checking for the WHERE-clause push-down optimization, verify that all terms of the compound inner SELECT are non-aggregate, not just the last term. Fix for ticket [f7f8c97e97597]. (check-in: [ec215f94ac] user: drh branch: trunk, size: 25483) | |
|
2016-03-15
| ||
| 17:52 | [d926792a5e] part of check-in [c7bae50bdc] Implement FROM-clause subqueries as co-routines whenever they are guaranteed to be the outer-most loop of the join. (check-in: [c7bae50bdc] user: drh branch: trunk, size: 24331) | |
|
2016-02-09
| ||
| 02:12 | [4536311585] part of check-in [ca72be8618] Make sure every co-routines has its own set of temporary registers and does not share temporaries, since a co-routine might expect the content of a temporary register to be preserved across an OP_Yield. Proposed fix for ticket [d06a25c84454a]. (check-in: [ca72be8618] user: drh branch: trunk, size: 23353) | |
|
2015-05-20
| ||
| 00:15 | [6d5bc6d178] part of check-in [c403502cdc] Fix handling of queries with VALUES on the left and UNION ALL SELECT on the right and a LIMIT clause. (check-in: [c403502cdc] user: drh branch: trunk, size: 22710) | |
|
2015-05-07
| ||
| 00:09 | [824342f382] part of check-in [5f2539da8c] Remove a faulty assert() statement. (check-in: [5f2539da8c] user: drh branch: trunk, size: 22517) | |
|
2015-05-04
| ||
| 16:09 | [ac1cd55264] part of check-in [1421c8ffba] Fix a faulty assert() in the SELECT code generator and add a test case to prevent regression. (check-in: [1421c8ffba] user: drh branch: trunk, size: 22429) | |
|
2015-04-21
| ||
| 02:17 | [48e14766d9] part of check-in [a526f58bc9] Test case for the previous check-in. (check-in: [a526f58bc9] user: drh branch: trunk, size: 22220) | |
|
2015-04-17
| ||
| 18:52 | [a3201fa921] part of check-in [6c39ef73d5] Always resolve symbols in all ORDER BY clauses of a compound-SELECT, even illegal ORDER BY clauses. (check-in: [6c39ef73d5] user: drh branch: trunk, size: 22109) | |
|
2015-04-16
| ||
| 16:22 | [4b2df48129] part of check-in [10715b05f2] Fix a faulty assert() in the compound-SELECT code generator. (check-in: [10715b05f2] user: drh branch: trunk, size: 21928) | |
| 14:13 | [d4330ee0e2] part of check-in [ec5a493ad2] Improvements to the way VALUES clauses are parsed. (check-in: [ec5a493ad2] user: drh branch: trunk, size: 21716) | |
|
2015-04-15
| ||
| 07:10 | [16fa1cafb9] part of check-in [14784c317b] Change the multiSelectOrderBy() routine to return non-zero if there has been any prior error. (check-in: [14784c317b] user: drh branch: trunk, size: 21490) | |
| 05:20 | [af938bb5f5] part of check-in [7c27310bdf] When adding the implied "LIMIT 1" to the end of a scalar subquery, make sure that subquery is not a VALUES-only query as such queries cannot deal with LIMIT clauses. (check-in: [7c27310bdf] user: drh branch: trunk, size: 21274) | |
|
2015-03-05
| ||
| 01:29 | [e20e8ce47b] part of check-in [e7991bc510] New requirements marks on compound SELECT statements. (check-in: [e7991bc510] user: drh branch: trunk, size: 21087) | |
|
2014-02-19
| ||
| 01:31 | [8c5a60d439] part of check-in [85b355cfb4] Make sure a multi-row VALUES clause works correctly in a compound SELECT. (check-in: [85b355cfb4] user: drh branch: trunk, size: 20950) | |
|
2012-03-03
| ||
| 01:44 | [00179be44e] part of check-in [4f34d7077b] Add a test case for ticket [3557ad65a076c]. (check-in: [4f34d7077b] user: drh branch: trunk, size: 19757) | |
|
2009-04-16
| ||
| 00:24 | [44aa6e7110] part of check-in [414f340809] In a 3-fold compound SELECT make sure early code generation of the SELECTs to the right do not dereference non-existant columns in SELECTs on the left. (CVS 6511) (check-in: [414f340809] user: drh branch: trunk, size: 19282) | |
|
2008-08-04
| ||
| 03:51 | [b64d5d248d] part of check-in [9ca975c8fd] Fix (make test) with SQLITE_OMIT_COMPOUND_SELECT. Ticket #3235. (CVS 5530) (check-in: [9ca975c8fd] user: danielk1977 branch: trunk, size: 18870) | |
|
2008-06-25
| ||
| 08:02 | [0618c93770] part of check-in [9902be8d66] Fixed typo to close #1731. (CVS 5302) (check-in: [9902be8d66] user: mihailim branch: trunk, size: 18867) | |
|
2008-03-26
| ||
| 12:46 | [7cc135c834] part of check-in [50de87dc80] Make sure an imbalance in the number of columns on a compound SELECT is detected and reported as an error before it can cause an assertion fault or array-bounds overflow in the code generator. Oops: part of the fix for ticket #3015 got included with this check-in by mistake. (CVS 4917) (check-in: [50de87dc80] user: drh branch: trunk, size: 18862) | |
|
2008-01-16
| ||
| 18:20 | [ba1c276ce2] part of check-in [3a289b6d28] Use 1<<$x instead of pow(2,$x) in the test suite code. (CVS 4715) (check-in: [3a289b6d28] user: danielk1977 branch: trunk, size: 15019) | |
|
2008-01-12
| ||
| 12:48 | [491193f507] part of check-in [a6dddebcc5] Continuing work toward converting the VM into a register machine. (CVS 4707) (check-in: [a6dddebcc5] user: drh branch: trunk, size: 15013) | |
|
2007-12-13
| ||
| 07:58 | [69015a6c02] part of check-in [2f88b9b3e3] Adjust the test suite to account for recent changes related to #2822. Most changes are related to English language error messages only. (CVS 4622) (check-in: [2f88b9b3e3] user: danielk1977 branch: trunk, size: 13952) | |
| 03:45 | [566b4ca115] part of check-in [56063ec84b] ORDER BY in a compound SELECT will first match against the left-most SELECT. If there is no match there, it begins working its way to the right. (CVS 4621) (check-in: [56063ec84b] user: drh branch: trunk, size: 13956) | |
|
2007-12-10
| ||
| 18:51 | [2dd28cfea6] part of check-in [0d9b0e6e3a] Further modifications to do with ORDER BY and compound SELECT queries. Related to ticket #2822. (CVS 4606) (check-in: [0d9b0e6e3a] user: danielk1977 branch: trunk, size: 13952) | |
|
2007-12-08
| ||
| 21:10 | [4192e6c712] part of check-in [62a78d212c] Better resolution of ORDER BY terms in compound queries. Candidate solution for ticket #2822. Needs more testing and documentation before going final. (CVS 4602) (check-in: [62a78d212c] user: drh branch: trunk, size: 13911) | |
|
2006-06-20
| ||
| 11:01 | [305ba0a6e9] part of check-in [c6ea353bd9] Modifications so that compilation and testing with the various OMIT macros defined works. (CVS 3276) (check-in: [c6ea353bd9] user: danielk1977 branch: trunk, size: 13919) | |
|
2006-03-26
| ||
| 01:21 | [d0280e3b6d] part of check-in [80cda9f7ce] SQLite now always chooses the column names for compound selects using 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) (check-in: [80cda9f7ce] user: drh branch: trunk, size: 13767) | |
|
2005-01-21
| ||
| 04:25 | [c239f516aa] part of check-in [d4e19efcef] Modify test scripts to work when SQLITE_OMIT_SUBQUERY (but no other OMIT macros) is defined. (CVS 2252) (check-in: [d4e19efcef] user: danielk1977 branch: trunk, size: 11784) | |
|
2004-11-22
| ||
| 13:35 | [1ae6f2bd61] part of check-in [007be591b7] Ensure tests pass when SQLITE_OMIT_COMPOUND_SELECT is defined. (CVS 2138) (check-in: [007be591b7] user: danielk1977 branch: trunk, size: 11482) | |
|
2004-05-27
| ||
| 17:22 | [86e72fc3b0] part of check-in [287f86731c] Remove the COPY command. (CVS 1477) (check-in: [287f86731c] user: drh branch: trunk, size: 11275) | |
|
2004-05-14
| ||
| 11:00 | [d2443e558c] part of check-in [dbfe6e9316] Implement type affinity for table and index records (CVS 1375) (check-in: [dbfe6e9316] user: danielk1977 branch: trunk, size: 11316) | |
|
2004-05-13
| ||
| 05:16 | [804b48d637] part of check-in [9f2b6d9d3a] Manifest types in indices. At the moment indices use manifest typing, but some other parts of the SQL engine do not, which can lead to some strange results. (CVS 1368) (check-in: [9f2b6d9d3a] user: danielk1977 branch: trunk, size: 11644) | |
|
2003-02-02
| ||
| 12:41 | [e7e9a32fa7] part of check-in [b687923158] Make the GROUP BY clause work even if there are no aggregate functions. (CVS 859) (check-in: [b687923158] user: drh branch: trunk, size: 11309) | |
|
2002-06-22
| ||
| 02:33 | [10ba54f24e] part of check-in [8aa73ce612] An optimization: avoid the use of an intermediate table on UNION ALL if there is no ORDER BY clause. (CVS 637) (check-in: [8aa73ce612] user: drh branch: trunk, size: 10698) | |
|
2002-06-20
| ||
| 03:38 | [13618c1107] part of check-in [43c5aff5d0] Fix for ticket #73: The ORDER BY clause is significant for subqueries. This passes all regression tests, but more testing is needed to exercise all paths through the new code. (CVS 631) (check-in: [43c5aff5d0] user: drh branch: trunk, size: 10345) | |
|
2002-06-02
| ||
| 16:09 | [9b5c87b7a3] part of check-in [7acbf84b49] Enhance the ORDER BY clause so that an integer term means to sort by the corresponding column. (CVS 602) (check-in: [7acbf84b49] user: drh branch: trunk, size: 8754) | |
|
2002-05-31
| ||
| 15:51 | [32018b97fd] part of check-in [da61aa1d23] Refinements to NULL processing: NULLs are indistinct for DISTINCT and UNION. Multiplying a NULL by zero yields zero. In a CASE expression, a NULL comparison is considered false, not NULL. With these changes, NULLs in SQLite now work the same as in PostgreSQL and in Oracle. (CVS 600) (check-in: [da61aa1d23] user: drh branch: trunk, size: 7655) | |
|
2002-05-27
| ||
| 01:04 | [2ea8c7b7fe] part of check-in [0e268d0c0f] Bug fixes and additional test cases for the distinct-NULL patch. (CVS 592) (check-in: [0e268d0c0f] user: drh branch: trunk, size: 7634) | |
|
2002-05-26
| ||
| 20:54 | [0bc0065102] part of check-in [9051173742] NULL values are distinct. A comparison involving a NULL is always false. Operations on a NULL value yield a NULL result. This change makes SQLite operate more like the SQL spec, but it may break existing applications that assumed the old behavior. All the old tests pass but we still need to add new tests to better verify the new behavior. Fix for ticket #44. (CVS 589) (check-in: [9051173742] user: drh branch: trunk, size: 7508) | |
|
2002-05-24
| ||
| 16:14 | [c2313f8c16] part of check-in [e238643efd] Add support for the full SQL join syntax. This is just a parser enhancement. We now recognize all kinds of joins, but we don't actually do anything with them yet. (CVS 586) (check-in: [e238643efd] user: drh branch: trunk, size: 6694) | |
|
2002-04-23
| ||
| 17:10 | [a8f1d97fbd] part of check-in [a06d9acdd5] Fix for ticket #22: In the code generator for compound SELECT statements, take care not to generate column name headers if the output is an intermediate table. Otherwise the column headers are not generated correctly if a compound SELECT statement appears as an expression in part of the WHERE clause. (CVS 543) (check-in: [a06d9acdd5] user: drh branch: trunk, size: 6691) | |
|
2001-09-16
| ||
| 00:13 | [29a2ffb187] part of check-in [4e926efe2b] Disclaimed copyright. Preparing for release 2.0. (CVS 250) (check-in: [4e926efe2b] user: drh branch: trunk, size: 5890) | |
|
2000-06-08
| ||
| 15:10 | [cb5374d7c8] part of check-in [61c381e7e6] :-) (CVS 81) (check-in: [61c381e7e6] user: drh branch: trunk, size: 6433) | |
| 01:55 | [5d6aa52fde] part of check-in [b3fb15ccde] :-) (CVS 77) (check-in: [b3fb15ccde] user: drh branch: trunk, size: 6048) | |
| 00:28 | Added: [c9b4b4ab9f] part of check-in [1902923308] :-) (CVS 76) (check-in: [1902923308] user: drh branch: trunk, size: 3169) | |