Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
50 most recent check-ins
|
2024-05-02
| ||
| 19:22 | Fix a problem with queries that use "IN(...) ORDER BY ... NULLS LAST" or similar introduced by [d7648e21605a0b38]. Leaf 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: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: b04e7a2347 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 | |
| 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: 7d30596496 user: dan tags: vtab-limit-fix | |
| 17:09 | Further fixes and improvements to the generate_series() enhancements on this branch. check-in: b7d9bd7ee2 user: drh tags: vtab-limit-fix | |
| 14:36 | Use hex flag masks rather than decimals in ext/misc/series.c. check-in: a94e2cd028 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: 72c8ed9698 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: 40421c1c4e 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: 408d47ecaa user: drh 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 | |
| 16:55 | Back out the previous change on this branch. In its place: Determine the affinity of a subquery by the left-most arm of the subquery that has an affinity other than NONE. In other words, scan from left to right looking for an arm of the compound subquery with an affinity of BLOB, TEXT, INTEGER, or REAL and pick the first one found. Or stay with NONE if no arm has a defined affinity. Test cases added. check-in: b8ec8511b1 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 | |
| 16:36 | If a RETURNING clause contains a subquery that references the table that is being updated in the statement that includes the RETURNING clause, then mark the subquery as correlated so that it is recomputed for each result and not just computed once and reused. See [forum:/forumpost/2c83569ce8945d39|forum post 2c83569ce8945d39]. check-in: 9ea6bcc8fd user: drh tags: trunk | |
| 14:18 | Fix a case where a corrupt stat4 record could go unrecognized due to integer overflow. check-in: 240a4a48b2 user: dan tags: trunk | |
| 11:51 | Add comments linking the assert() added in [cef4d9e3ba586735] to the places where the precondition that the assert() tests are actually required. check-in: 6f0e7e1952 user: drh tags: trunk | |
| 11:40 | Avoid slowdown when exprNodeIsConstant() is called on deeply nested SQL functions. check-in: 1c0b034545 user: dan tags: trunk | |
| 11:21 | Ensure that temporary SrcItem objects created by trigger processing have either SrcItem.zName or SrcItem.pSelect defined. Every SrcItem should have one or the other. check-in: cef4d9e3ba user: drh tags: trunk | |
| 06:43 | Remove an undocumented feature from the JS Worker1.open API because it relies on broken behavior which has no VFS-agnostic workaround. check-in: 3a640038c7 user: stephan tags: trunk | |
|
2024-04-23
| ||
| 12:02 | Fix a problem with vector IN operators used with an index where the affinities and collations for the various vector terms are different. check-in: 86e8c782e7 user: drh tags: trunk | |
| 11:56 | Fix an uninitialized variable problem in the new code on this branch. Closed-Leaf check-in: 85625b3871 user: dan tags: vector-in-fix | |
| 06:49 | Remove some dead WASM-side code. check-in: 0a07ee27bd user: stephan tags: trunk | |
| 06:36 | Minor touchups in JS docs and exception messages. check-in: 9e7fc9370d user: stephan tags: trunk | |
| 05:38 | When running the 'dist' target in ext/wasm for an SEE-capable build, ensure that the resulting zip file and directory name include '-see'. check-in: 04c552b12e user: stephan tags: trunk | |
|
2024-04-22
| ||
| 20:09 | Add extra tests for aborting conflicts in the sessions module. check-in: b4a6d32662 user: dan tags: trunk | |
| 17:03 | Minor cleanups to [8fbda563d2f5]. check-in: 5ee2594b65 user: stephan tags: trunk | |
| 16:46 | Extend the JS/WASM SEE build support by (A) filtering SEE-related bits out of the JS when not building with SEE and (B) accepting an optional key/textkey/hexkey option to the sqlite3.oo1.DB and subclass constructors to create/open SEE-encrypted databases with. Demonstrate SEE in the test app using the kvvfs. This obviates the changes made in [5c505ee8a7]. check-in: 8fbda563d2 user: stephan tags: trunk | |
| 13:31 | Extra robustness in the code that causes cursors to return NULL when they are participating in an OUTER JOIN. check-in: 672c2869ef user: drh tags: trunk | |
| 11:48 | For sqlite3.oo1.DB JavaScript classes, bypass execution of any on-open() SQL in SEE-capable builds because it would necessarily run before the client has an opportunity to provide their decryption key, which would leave the db handle in an unusable state and cause the ctor to throw. This currently affects only the OPFS VFSes. We may want to consider extending the ctor options object to optionally accept an SEE key and apply it when opening the db. check-in: 5c505ee8a7 user: stephan tags: trunk | |
| 00:42 | Continuation of the fix at [8c0f69e0e4ae0a44]: If a viaCoroutine FROM clause term is participating in a RIGHT or FULL JOIN, we have to create an always-NULL pseudo-cursor for that term when processing the RIGHT join. dbsqlfuzz 6fd1ff3a64bef4a6c092e8d757548e95698b0df5. check-in: e1040e51eb user: drh tags: trunk | |
|
2024-04-21
| ||
| 23:35 | Fix an indentation problem in debugging routine sqlite3ShowSrcList(). No changes to production code. check-in: 5560df2726 user: drh tags: trunk | |
|
2024-04-20
| ||
| 19:19 | Slight performance improvement for the new code on this branch. check-in: 500c67f134 user: dan tags: vector-in-fix | |
| 15:14 | Fix a problem where an expression like (a, b) IN (SELECT ...) might not use an index on (a, b) if the affinities and collation sequences of "a" and "b" are not identical. check-in: 4d870fd8b5 user: dan tags: vector-in-fix | |
|
2024-04-18
| ||
| 16:11 | Correct handling of OUTER JOIN when on or the other operand is a subquery implemented using the VALUES-as-coroutine optimization. dbsqlfuzz bde3bf80aedf25afa56e2997a0545a314765d3f8. check-in: 8c0f69e0e4 user: drh tags: trunk | |