Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
50 most recent check-ins related to "trunk"
|
2024-05-13
| ||
| 20:06 | Allow existing fts5 tables to be dropped even if the associated tokenizer is not available. (Leaf check-in: 69ef47eeee user: dan tags: fts5-delay-tokenizer) | |
|
2024-05-12
| ||
| 00:26 | Optimization in the implementation of OP_OpenRead and OP_OpenWrite (Leaf check-in: 3a256a1667 user: drh tags: faster-openread) | |
|
2024-05-11
| ||
| 16:44 | Add tests to bestindexC.test. No changes to code. (Leaf check-in: 58d938c0e0 user: dan tags: trunk) | |
|
2024-05-10
| ||
| 18:24 | Fix aggregate function processing to correctly deal with OOMs inside of sqlite3ParserAddCleanup(). (dbsqlfuzz b2d11ca70e55ee8bde48ae0b53fa3e9355812f95). Also add improved testing support by causing sqlite3FaultSim(300) to simulate an OOM inside of sqlite3ParserAddCleanup() and by adding improved fault-sim support to the CLI. (check-in: c6fd70b3c2 user: drh tags: trunk) | |
| 18:15 | Add a test for the fixes on this branch. (Closed-Leaf check-in: 716088d673 user: dan tags: cleanup-testing) | |
| 16:28 | Add an sqlite3FaultSim(300) call to the sqlite3ParserAddCleanup() routine for more precise simulation of OOM errors in that routine. (check-in: 1e8863909a user: drh tags: cleanup-testing) | |
| 09:26 | Squelch two OMIT-flag-related warnings reported in [forum:388243d9882067a9|forum post 388243d9882067a9]. No functional changes. (check-in: 1d6716054d user: stephan tags: trunk) | |
|
2024-05-09
| ||
| 18:54 | Reformulate a for-in loop to a for loop in wasm.xWrap() to work around downstream frameworks modifying the JS Array prototype, as reported in [forum:b549992634b55104|forum post b549992634b55104]. (Leaf check-in: ce2eb6d89a user: stephan tags: branch-3.45) | |
| 18:39 | Add a maintenance-reminder comment explaining [dc58ed65492857]. (check-in: 857f5d7fad user: stephan tags: trunk) | |
| 18:00 | Reformulate a for-in loop to a for loop in wasm.xWrap() to work around downstream frameworks modifying the JS Array prototype, as reported in [forum:b549992634b55104|forum post b549992634b55104]. (check-in: dc58ed6549 user: stephan tags: trunk) | |
| 17:45 | Fix a problem causing the recovery extension to use excessive memory and CPU time in some cases. (check-in: bc394acb6e user: dan tags: branch-3.45) | |
|
2024-05-08
| ||
| 17:57 | Rename a shadowed local var, as reported in [forum:2ba65af3148585cf|forum post 2ba65af31]. No functional changes. (check-in: d030c87c4d user: stephan tags: trunk) | |
| 17:42 | Allow arbitrary expressions as the second argument to RAISE(). (Leaf check-in: 003e1c8c27 user: drh tags: enhanced-raise) | |
| 11:51 | Fix a hyperlink typo in session documentation. (check-in: 42d67c6fed user: drh tags: trunk) | |
|
2024-05-07
| ||
| 19:45 | Fix bug in test script sessionconflict.test. (check-in: e29decb8b1 user: dan tags: trunk) | |
| 17:58 | Ensure successive scans of pragma virtual tables return consistent rowids. (check-in: 6838bf3ac1 user: dan tags: trunk) | |
| 13:20 | Fix a compilation error in test/lemon-test01.y, reported in [forum:f0ad095705|forum post f0ad095705]. (check-in: 576b68c8b5 user: stephan tags: trunk) | |
|
2024-05-06
| ||
| 20:21 | When extracting links from sqlar archives, clobber any existing file or link, and do not call utimes() to set the timestamp - it looks through the link and operates on the target. (check-in: 2bf8c3f99a user: dan tags: trunk) | |
| 20:18 | Omit redundant unary + operators from the AST. (check-in: f81cc149e5 user: drh tags: trunk) | |
| 19:04 | Avoid unnecessary recursion in sqlite3ExprDeleteNN(). This complicates the code, but it is needed to prevent nuisance "stack overflow" reports from OSSFuzz while it is running the latest ASAN. (check-in: 70abc144ca user: drh tags: trunk) | |
| 17:55 | Add new sessions API sqlite3changegroup_add_change(). (check-in: 5eaab43ce4 user: dan tags: trunk) | |
| 17:32 | Edit comments in sqlite3session.h. (Closed-Leaf check-in: 49f84878e2 user: dan tags: changegroup-add-change) | |
| 11:27 | Fix problem in sqlar_uncompress() when being used to extract symbolic links. (check-in: 4d90c3f179 user: dan tags: trunk) | |
|
2024-05-05
| ||
| 10:00 | Add comment to the test/lemon-test01.y file indicating that it does not work and is for historical reference only. (check-in: 9bdf73a8d4 user: drh tags: trunk) | |
|
2024-05-04
| ||
| 21:10 | Add new sessions API sqlite3changegroup_add_change(). (check-in: 73647db1dd user: dan tags: changegroup-add-change) | |
| 16:50 | Add test cases to test/in7.test. No code changes. (check-in: 8c3086f9fe 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: b36d499e4c 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: f16b200f25 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: cdd1610c44 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: 26b2d9390f user: dan tags: trunk) | |
| 18:16 | Avoid an assert failure accessible only when internal testing features are enabled. dbsqlfuzz crash-66abacda6bca6bd531e25595e8c8068e2c710326.txt. (check-in: fbc446daac user: dan tags: trunk) | |
| 17:46 | Fix a case where the recovery extension might write uninitialized data to the recovered database. (check-in: 8519b4d039 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: d7648e2160 user: dan tags: trunk) | |
| 12:14 | Fix the CREATE TABLE performance issue described by [forum:/forumpost/4cf69794d9dfff7c|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: 71f08b9122 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: 39a57b596d 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: 532795acd1 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: 560f64157d 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: 1c7e33a8aa 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: 8de85170d5 user: dan tags: trunk) | |
|
2024-04-30
| ||
| 19:34 | Avoid 32-bit overflow when calculating ncycle for ".scanstats vm". (check-in: 2858efa06d user: dan tags: trunk) | |
|
2024-04-26
| ||
| 19:10 | Fix issues in [/info/1e227ad9f413227f|LIMIT/OFFSET support for virtual tables]. The first problem was reported by [forum:/forumpost/c243b8f856|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: 5f6c079d84 user: drh tags: trunk) | |
| 18:42 | Internal JS doc touchups. No functional changes. (check-in: 626b997b4e user: stephan tags: trunk) | |
| 18:24 | Additional internal docs in the wasm utilities. (check-in: 5a2245a9eb 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: 90e5c8226a user: dan tags: vtab-limit-fix) | |
| 12:01 | Add test demonstrating the problem at [forum:/forumpost/c243b8f856|forum post c243b8f856]. No fix yet. (check-in: 1685495c0a 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: 38f1e5ce4e 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: e6df846f36 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: bbdf22e3d9 user: drh tags: compound-subquery-affinity) | |
| 06:52 | wasm: add a makefile comment about the static sqlite3.h/c version info injected into the JS files possibly differing from the runtime-emited version info when a user provides their own sqlite3.c. (check-in: d99a01a0f6 user: stephan tags: trunk) | |
|
2024-04-24
| ||
| 19:49 | An experimental minor tweak to the way affinities are computed for compound subqueries, when the actual affinity is ambiguous. (check-in: 779723ad79 user: drh tags: compound-subquery-affinity) | |