Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
30 ancestors of trunk
|
2024-05-04
| ||
| 16:50 | Add test cases to test/in7.test. No code changes. Leaf check-in: 8c3086f9 user: dan tags: trunk | |
| 15:10 | Assume that an SQL function is able to return a subtype if any of its arguments are SQL functions that are able to return subtypes. This closes a corner-case hole in the patch at [ba789a7804ab96d8]. check-in: b36d499e user: drh tags: trunk | |
| 15:04 | Assume that a function is able to return a subtype if either (1) it is itself marked with SQLITE_RESULT_SUBTYPE, or (2) one of its arguments is a function that is able to return a subtype. This check-in backs out the code changes from the previous two on this same branch, but keeps the test cases from the previous two. Closed-Leaf check-in: f16b200f user: drh tags: func-rw-subtype | |
| 11:31 | Functions that pass through the sqlite3_value of one of their arguments must also be marked as SQLITE_RESULT_SUBTYPE, in case one of their arguments has a subtype. check-in: 2f9fba93 user: drh tags: func-rw-subtype | |
|
2024-05-03
| ||
| 19:35 | The coalesce(), ifnull(), and iif() functions pass through subtype values from their arguments, and hence need to have the SQLITE_RESULT_SUBTYPE flag set. check-in: cdd1610c user: drh tags: func-rw-subtype | |
|
2024-05-02
| ||
| 19:22 | Fix a problem with queries that use "IN(...) ORDER BY ... NULLS LAST" or similar introduced by [d7648e21605a0b38]. check-in: 26b2d939 user: dan tags: trunk | |
| 18:16 | Avoid an assert failure accessible only when internal testing features are enabled. dbsqlfuzz crash-66abacda6bca6bd531e25595e8c8068e2c710326.txt. check-in: fbc446da user: dan tags: trunk | |
| 17:46 | Fix a case where the recovery extension might write uninitialized data to the recovered database. check-in: 8519b4d0 user: dan tags: trunk | |
| 14:48 | Avoid an OP_Next in cases where an IN(...) query against a UNIQUE index may return at most 1 row. check-in: d7648e21 user: dan tags: trunk | |
| 12:14 | Fix the CREATE TABLE performance issue described by forum thread 4cf69794d9dfff7c in two different ways: (1) Omit the call to PRAGMA integrity_check('X') that was being done after CREATE TABLE "X" because the result was being ignored and the integrity_check was not doing anything other than burning CPU cycles. (2) Do not interpret the argument to PRAGMA integrity_check as a number if it is in fact a string that looks like a number. check-in: 71f08b91 user: drh tags: trunk | |
| 12:00 | Add a test case to the fix to PRAGMA integrity_check in the previous check-in. Closed-Leaf check-in: 39a57b59 user: drh tags: faster-create | |
| 11:52 | Do not accept a string that looks like a number used as an argument to PRAGMA integrity_check as a number. Treat it as a table name that just happens to look like a number. check-in: b04e7a23 user: drh tags: faster-create | |
| 11:51 | Omit the OP_SqlExec to "PRAGMA integrity_check" added by [348fa7aaf7958b3f] because it is a no-op. Even if the integrity_check failes, the CREATE TABLE is stull successful. The OP_SqlExec just burns CPU cycles for no reason. check-in: 532795ac user: drh tags: faster-create | |
|
2024-05-01
| ||
| 19:48 | Avoid an OP_Next in cases where an IN(...) query against a UNIQUE index may return at most 1 row. Closed-Leaf check-in: 560f6415 user: dan tags: unique-in-opt | |
| 16:25 | Fix another problem in the recovery extension where a corrupt sqlite_schema table could lead to excessive memory consumption. check-in: 1c7e33a8 user: dan tags: trunk | |
| 14:42 | Fix a problem causing the recovery extension to use excessive memory and CPU time in some cases. check-in: 8de85170 user: dan tags: trunk | |
|
2024-04-30
| ||
| 19:34 | Avoid 32-bit overflow when calculating ncycle for ".scanstats vm". check-in: 2858efa0 user: dan tags: trunk | |
|
2024-04-26
| ||
| 19:10 | Fix issues in LIMIT/OFFSET support for virtual tables. The first problem was reported by forum post c243b8f856. That report prompted an enhancement to the generate_series() (also included in this merge) which in turn identified other similar issues. check-in: 5f6c079d user: drh tags: trunk | |
| 18:42 | Internal JS doc touchups. No functional changes. check-in: 626b997b user: stephan tags: trunk | |
| 18:24 | Additional internal docs in the wasm utilities. check-in: 5a2245a9 user: stephan tags: trunk | |
| 18:13 | Allow virtual table implementations to handle OFFSET but not LIMIT, but not LIMIT but not OFFSET. Closed-Leaf check-in: 90e5c822 user: dan tags: vtab-limit-fix | |
| 17:19 | Have where.c ignore any plan from a virtual table that tries to use LIMIT/OFFSET without also using all WHERE constraints. check-in: 7d305964 user: dan tags: vtab-limit-fix | |
| 17:09 | Further fixes and improvements to the generate_series() enhancements on this branch. check-in: b7d9bd7e user: drh tags: vtab-limit-fix | |
| 14:36 | Use hex flag masks rather than decimals in ext/misc/series.c. check-in: a94e2cd0 user: drh tags: vtab-limit-fix | |
| 14:32 | Fix a problem allowing a LIMIT constraint to be passed to a virtual table in cases where there exist WHERE terms that cannot also be passed. check-in: 72c8ed96 user: dan tags: vtab-limit-fix | |
| 13:38 | Fix handling of LIMIT and OFFSET in virtual tables that are part of a compound SELECT. check-in: 40421c1c user: drh tags: vtab-limit-fix | |
| 13:30 | Enhance the generated_series() table-valued-function to respond to LIMIT and OFFSET. Use this to add new test cases for LIMIT and OFFSET on virtual tables in a compound SELECT. check-in: 408d47ec user: drh tags: vtab-limit-fix | |
| 12:01 | Add test demonstrating the problem at forum post c243b8f856. No fix yet. check-in: 1685495c user: dan tags: vtab-limit-fix | |
| 11:32 | Fix the TreeView display of a LIMIT clause on a compound query. Debugging code only - not part of production builds. check-in: 38f1e5ce user: drh tags: trunk | |
|
2024-04-25
| ||
| 23:26 | Improvement to the way that affinity is determined for columns of a compound subquery. The affinity is the affinity of the left-most arm of the compound subquery that has an affinity other than NONE, adjusted to accommodate the data types coming out of the other arms. check-in: e6df846f user: drh tags: trunk | |
| 17:52 | Further improvements to the computation of affinity for compound subqueries: 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. Closed-Leaf check-in: bbdf22e3 user: drh tags: compound-subquery-affinity | |