Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
200 most recent check-ins using file test/unionvtabfault.test version e8759f3d
|
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. (Leaf 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) | |
| 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: b8ec8511 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: d99a01a0 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: 779723ad 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 post 2c83569ce8945d39. (check-in: 9ea6bcc8 user: drh tags: trunk) | |
| 14:18 | Fix a case where a corrupt stat4 record could go unrecognized due to integer overflow. (check-in: 240a4a48 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: 6f0e7e19 user: drh tags: trunk) | |
| 11:40 | Avoid slowdown when exprNodeIsConstant() is called on deeply nested SQL functions. (check-in: 1c0b0345 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: cef4d9e3 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: 3a640038 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: 86e8c782 user: drh tags: trunk) | |
| 11:56 | Fix an uninitialized variable problem in the new code on this branch. (Closed-Leaf check-in: 85625b38 user: dan tags: vector-in-fix) | |
| 06:49 | Remove some dead WASM-side code. (check-in: 0a07ee27 user: stephan tags: trunk) | |
| 06:36 | Minor touchups in JS docs and exception messages. (check-in: 9e7fc937 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: 04c552b1 user: stephan tags: trunk) | |
|
2024-04-22
| ||
| 20:09 | Add extra tests for aborting conflicts in the sessions module. (check-in: b4a6d326 user: dan tags: trunk) | |
| 17:03 | Minor cleanups to [8fbda563d2f5]. (check-in: 5ee2594b 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: 8fbda563 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: 672c2869 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: 5c505ee8 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: e1040e51 user: drh tags: trunk) | |
|
2024-04-21
| ||
| 23:35 | Fix an indentation problem in debugging routine sqlite3ShowSrcList(). No changes to production code. (check-in: 5560df27 user: drh tags: trunk) | |
|
2024-04-20
| ||
| 19:19 | Slight performance improvement for the new code on this branch. (check-in: 500c67f1 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: 4d870fd8 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: 8c0f69e0 user: drh tags: trunk) | |
|
2024-04-17
| ||
| 19:48 | Prevent tokenize-blobs from being used with non-contentless tables. Fix some other issues with the new code on this branch. (Leaf check-in: 6a640ea4 user: dan tags: fts5-tokenize-blob) | |
|
2024-04-16
| ||
| 14:23 | Add some tests for the fts5 tokenize-blob functionality on this branch. (check-in: c2f9d125 user: dan tags: fts5-tokenize-blob) | |
|
2024-04-15
| ||
| 20:43 | The first assert() added in [0ebc65481f4a3e79] is not necessarily true in a corrupt database file. So add a term to make it true. (check-in: 6b21cccd user: drh tags: trunk) | |
| 20:24 | Add experimental way to specify an alternative tokenizer when writing to or querying an fts5 table. (check-in: 6c51c9c6 user: dan tags: fts5-tokenize-blob) | |
| 14:59 | Merge version 3.45.3 patches into the reuse-schema-3.45 sub-branch. (Leaf check-in: a1ff4153 user: drh tags: reuse-schema-3.45) | |
| 14:45 | Merge all of the latest trunk enhancements into the bedrock branch. (Leaf check-in: 16dac180 user: drh tags: bedrock) | |
| 14:39 | Merge the latest trunk enhancements into the wal2 branch. (Leaf check-in: 4a72acbc user: drh tags: wal2) | |
| 14:36 | Merge the latest trunk enhancements into the begin-concurrent branch. (Leaf check-in: eedf6bed user: drh tags: begin-concurrent) | |
| 14:29 | Merge from wrong branch. Bedrock should be updated from wal2, not from trunk. (Closed-Leaf check-in: 4c23cad9 user: drh tags: mistake) | |
| 14:21 | Merge all 3.45.3 changes into the wal2-3.45 branch. (Leaf check-in: 2ccc0185 user: drh tags: wal2-3.45) | |
| 14:18 | Merge all 3.45.3 changes into the begin-concurrent-3.45 subbranch. (Leaf check-in: 3dda82e0 user: drh tags: begin-concurrent-3.45) | |
| 13:34 | Version 3.45.3 (Leaf check-in: 8653b758 user: drh tags: release, branch-3.45, version-3.45.3) | |
|
2024-04-12
| ||
| 18:46 | If a build fails in testrunner.tcl, do not attempt to run the jobs that depend on that build. Instead, report those jobs as having been skipped. (check-in: b40580be user: drh tags: trunk) | |
| 16:52 | Adjustment to EQP output in one test case. (check-in: 08dd2b92 user: drh tags: branch-3.45) | |
| 15:15 | Mark the BTree cell overflow cache as invalid whenever the rowid goes invalid. (Leaf check-in: 0ec6669c user: drh tags: branch-3.44) | |
| 15:10 | Increase the version number to 3.45.3. (check-in: 119b3b3c user: drh tags: branch-3.45) | |
| 15:06 | Mark the BTree cell overflow cache as invalid whenever the rowid goes invalid. (check-in: 5266bb6d user: drh tags: branch-3.45) | |
| 15:02 | Fixes and new tests logic to ensure that the btree overflow page cache is only used when it is consistent. This resolves the malfunction observed in forum post 284955a3cd454a15. (check-in: 5dede50d user: drh tags: trunk) | |
| 13:05 | Add assert() statements to help verify the overflow page cache. (Closed-Leaf check-in: 0ebc6548 user: drh tags: btree-ovfl-cache) | |
| 12:32 | New assert() statements to verify the correctness of the BTCF_AtLast flag on btree cursors. (check-in: 4efecd61 user: drh tags: btree-ovfl-cache) | |
| 11:28 | Test case for the fix in the previous check-in. (check-in: 0cf4d835 user: drh tags: btree-ovfl-cache) | |
| 02:57 | Mark the BTree cell overflow cache as invalid whenever the rowid goes invalid. (check-in: 74c9e19c user: drh tags: btree-ovfl-cache) | |
|
2024-04-11
| ||
| 19:09 | Fix handling of the SQLITE_OMIT_WAL check in one place. Resolves forum post 87cc13302de160eb. (check-in: ce86d30d user: stephan tags: branch-3.45) | |
| 19:08 | Fix handling of the SQLITE_OMIT_WAL check in one place. Resolves forum post 87cc13302de160eb. (check-in: 5dae6e6d user: stephan tags: trunk) | |
|
2024-04-10
| ||
| 16:36 | Fix the pragma4.test script so that it works with SQLITE_OMIT_VIRTUALTABLE. (check-in: 61060c7d user: dan tags: branch-3.45) | |
|
2024-04-09
| ||
| 19:23 | Fix a "shift exponent is too large" usan error that could occur in the fts3 snippet() function when a query phrase contains more than 64 tokens. (check-in: 6d2c7ac4 user: dan tags: trunk) | |
| 15:18 | Avoid some performance problems in the recover extension when recovering strategically corrupted databases. (check-in: d83b0ffe user: dan tags: branch-3.45) | |
| 15:09 | Avoid some performance problems in the recover extension when recovering strategically corrupted databases. (check-in: e66a834b user: dan tags: trunk) | |
| 14:08 | Ignore CHECK constraints when qualifying the xfer optimization while running VACUUM. (check-in: 944d1b6e user: drh tags: branch-3.44) | |
| 14:07 | Ignore CHECK constraints when qualifying the xfer optimization while running VACUUM. (check-in: bb6f9908 user: drh tags: branch-3.45) | |
| 13:57 | The read-only CHECK-constraint optimization of [34ddf02d3d21151b] inhibits the xfer optimization for tables with CHECK constraints. However, the xfer optimization is required for correct operation of VACUUM INTO on tables that contain generated columns. Fix this by ignoring CHECK constraints when qualifying the xfer optimization while running VACUUM. Problem reported by forum post 3ec177d68fe7fa2c. (check-in: a6e26e77 user: drh tags: trunk) | |
|
2024-04-08
| ||
| 17:55 | Update tests in returning1.test to account for [c7896e88]. (check-in: c02956cd user: dan tags: trunk) | |
| 12:02 | Merge the latest trunk enhancements, and especially the enhancement to the WHERE-clause push-down optimization, into the bedrock branch. (check-in: 0f93b52c user: drh tags: bedrock) | |
| 11:57 | Merge the latest trunk enhancements into the wal2 branch. (check-in: 59ccea7d user: drh tags: wal2) | |
| 11:50 | Enhance the WHERE-clause push-down optimization so that it is able to push down WHERE clause terms that contain uncorrelated subqueries. (check-in: 69ec714b user: drh tags: trunk) | |
| 11:45 | Fix a harmless compiler warning in the ICU extension due to [acddbc489d5231da]. (check-in: 3d8750e8 user: drh tags: trunk) | |
| 06:37 | Enhancements to the fuzzer invariant checker to turn optimizations on and off. (Closed-Leaf check-in: 67594481 user: drh tags: pushdown-subquery) | |
|
2024-04-07
| ||
| 18:55 | Merge trunk testing enhancements into the pushdown-subquery branch. (check-in: 287ff24b user: drh tags: pushdown-subquery) | |
| 18:36 | Omit all rowid-in-view restrictions from the fuzzinvariant.c test module as they are no longer necessary, as of the previous check-in. (check-in: 6431538f user: drh tags: trunk) | |
| 18:23 | If SQLITE_ALLOW_ROWID_IN_VIEW is set to 2, then all rowids for views return a value of NULL. (check-in: 0a53dde2 user: drh tags: trunk) | |
| 10:30 | Merge trunk enhancements into the pushdown-subquery branch. (check-in: 27865e31 user: drh tags: pushdown-subquery) | |
| 10:27 | Add comments to note the name abiguity between the MySQL push-down optimization and the WHERE-clause push-down optimization. (check-in: 3d5fb1ec user: drh tags: trunk) | |
|
2024-04-06
| ||
| 23:09 | Add comments to note the name abiguity between the MySQL push-down optimization and the WHERE-clause push-down optimization. (Leaf check-in: 681dfe2d user: drh tags: wrong-branch) | |
| 18:30 | Do not allow changes to sqlite3ExprIsTableConstant() that support pushdown of subqueries interfere with the hash-join logic. (check-in: 8682931f user: drh tags: pushdown-subquery) | |
| 17:42 | Merge testing logic fixes on trunk into the pushdown-subquery branch. (check-in: a4e1f03d user: drh tags: pushdown-subquery) | |
| 17:37 | Improvements to the accurancy of the fuzzinvariants.c testing module when SQLITE_ALLOW_ROWID_IN_VIEW is defined and the test query involves rowids. (check-in: c6e873d4 user: drh tags: trunk) | |
| 12:19 | Generalize pushdown to allow any uncorrelated subquery to be pushed down. (check-in: 87c45fb0 user: drh tags: pushdown-subquery) | |
| 11:59 | Generalize the pushdown of IN right-hand sides to cover more SELECTs. (Closed-Leaf check-in: 4120bc74 user: drh tags: pushdown-IN-table) | |
|
2024-04-05
| ||
| 20:01 | Experimental enhancement in which expressions of the form "expr IN table" can be pushed down into subexpressions. (check-in: 2cbd7838 user: drh tags: pushdown-IN-table) | |
| 15:04 | Merge all recent trunk enhancements into the reuse-schema branch. (Leaf check-in: e556f3d3 user: drh tags: reuse-schema) | |
| 14:54 | Merge the latest trunk enhancements into the bedrock branch. (check-in: 7a2a64b6 user: drh tags: bedrock) | |
| 14:50 | Merge the latest trunk enhancements into the wal2 branch. (check-in: a8a8a2db user: drh tags: wal2) | |
| 14:46 | Merge the latest trunk enhancements into the begin-concurrent branch. (check-in: 4ff83342 user: drh tags: begin-concurrent) | |
| 14:13 | Check-in a9657c87c53c1922 is wrong: the IndexedExpr.bMaybeNullRow flag is required for virtual columns if they are part of an outer join. Add a test case to prove it. (check-in: 083b0f7e user: drh tags: branch-3.44) | |
| 14:06 | Fix obscure issues associated with SQLITE_ALLOW_ROWID_IN_VIEW and indexes on virtual columns in a RIGHT JOIN. (check-in: 4b3a253f user: drh tags: branch-3.45) | |
| 13:56 | Check-in [a9657c87c53c1922] is wrong: the IndexedExpr.bMaybeNullRow flag is required for virtual columns if they are part of an outer join. Add a test case (derived from dbsqlfuzz b9e65e2f110df998f1306571fae7af6c01e4d92b) to prove it. (check-in: 4484ec6d user: drh tags: trunk) | |
| 11:28 | When compiling with SQLITE_ALLOW_ROWID_IN_VIEW, if the RETURNING clause of an UPDATE of a view specifies a rowid, then return NULL for the value of that rowid. (check-in: d38cfa60 user: drh tags: branch-3.44) | |
| 11:23 | When compiling with SQLITE_ALLOW_ROWID_IN_VIEW, if the RETURNING clause of an UPDATE of a view specifies a rowid, then return NULL for the value of that rowid. dbsqlfuzz 7863696e9e5ec10b29bcf5ab2681cd6c82a78a4a. (check-in: c7896e88 user: drh tags: trunk) | |
|
2024-04-04
| ||
| 22:53 | Optimize sqlite3.oo1.DB.exec() for the rowMode='object' case to avoid converting the object property keys (column names) from native code to JS for each row. This speeds up large data sets considerably and addresses the report in forum post 3632183d2470617d. (check-in: 8b41ef86 user: stephan tags: trunk) | |
| 14:26 | Add the "interstage-heuristic" that attempts to avoid wildly inefficient queries that use table scans instead of index lookups because the output row estimates are inaccurate. (check-in: 7bf49e2c user: drh tags: trunk) | |
| 13:36 | Fix an ASAN problem in part of the test harness. No changes to SQLite itself. (check-in: 797cda7d user: drh tags: trunk) | |
| 13:07 | Fix test cases due to an error message change. (check-in: c49ec239 user: drh tags: trunk) | |
| 12:37 | Fix exception propagation when the opfs-sahpool VFS fails to initialize to address report in forum post be0141c639. (check-in: db31d178 user: stephan tags: branch-3.45) | |
| 12:36 | Fix exception propagation when the opfs-sahpool VFS fails to initialize to address report in forum post be0141c639. (check-in: cdb3a900 user: stephan tags: trunk) | |
|
2024-04-02
| ||
| 21:55 | Add an optional 3rd argument to the icu_load_collation() function that specifies the "strength" of the comparison. (check-in: acddbc48 user: drh tags: trunk) | |
| 18:48 | Fix typos in comments. Provided ".wheretrace" debugging output for the interstage heuristic module. Do omit automatic index loops in the interstage heuristic. (Leaf check-in: 357d9513 user: drh tags: branch-3.28) | |
| 18:31 | Fix table-valued functions so that they will work as the right table in a LEFT JOIN. Ticket [2ae0c599b735d59e] (check-in: 1f97086d user: drh tags: branch-3.28) | |
| 14:12 | Fix typos in comments. Provided ".wheretrace" debugging output for the interstage heuristic module. Do omit automatic index loops in the interstage heuristic. (Closed-Leaf check-in: 186dcae1 user: drh tags: interstage-heuristic) | |
| 11:54 | Add a heuristic in between the two solver() passes of the query planner that tries to prevent a very slow query plan in cases where the output row count estimate is imprecise. (check-in: 74b247d9 user: drh tags: branch-3.28) | |
| 11:44 | Add a heuristic in between the two solver() passes of the query planner that tries to prevent a very slow query plan in cases where the output row count estimate is imprecise. (check-in: 8018417b user: drh tags: interstage-heuristic) | |
|
2024-04-01
| ||
| 15:38 | Improved comments in the query planner logic that computes the cost for a particular step in a query plan. No code changes. (check-in: 0b2ac2cd user: drh tags: trunk) | |
|
2024-03-30
| ||
| 14:11 | Make explicit that sqlite3_keyword_name()'s index is 0-based, per forum request. Doc changes only. (check-in: 090943dc user: stephan tags: trunk) | |
|
2024-03-29
| ||
| 18:19 | Fix handling of an OOM case broken by [11015b4e]. (check-in: 1f3a805d user: dan tags: bedrock) | |
| 18:16 | Fix handling of an OOM case broken by [49263c91]. (check-in: 9e6b64de user: dan tags: begin-concurrent) | |
| 18:07 | Fix a problem in SQLITE_DIRECT_OVERFLOW_READ builds that could allow a concurrent transaction to be committed even if it read from an overflow page that was modified concurrently, in cases where the overflow page was written without also writing the b-tree page to which it is linked. (check-in: 11015b4e user: dan tags: bedrock) | |
| 18:04 | Improve the log message emitted when a BEGIN CONCURRENT transaction cannot be committed due to conflicts so that it identifies the conflicting table in a few more cases. (check-in: 19ff2d4e user: dan tags: bedrock) | |
| 17:58 | Fix a problem in SQLITE_DIRECT_OVERFLOW_READ builds that could allow a concurrent transaction to be committed even if it read from an overflow page that was modified concurrently, in cases where the overflow page was written without also writing the b-tree page to which it is linked. (check-in: 49263c91 user: dan tags: begin-concurrent) | |
| 17:32 | Improve the log message emitted when a BEGIN CONCURRENT transaction cannot be committed due to conflicts so that it identifies the conflicting table in a few more cases. (check-in: 5d30e362 user: dan tags: begin-concurrent) | |
|
2024-03-28
| ||
| 10:58 | Document that the order of an update hook call is unspecied vis-a-vis the final result of the operation which triggers that hook. Doc changes only. (check-in: 3d4b1f07 user: stephan tags: trunk) | |
|
2024-03-27
| ||
| 20:34 | Update comments in fts5.h. (check-in: 862945d5 user: dan tags: trunk) | |
|
2024-03-26
| ||
| 18:07 | Add extra tests to vtabL.test. (check-in: fe209099 user: dan tags: trunk) | |
| 11:14 | Avoid expanding integer values in columns with real affinity to the full 8-byte representation when editing records as part of a DROP COLUMN command. (check-in: a49296de user: dan tags: trunk) | |
| 10:48 | Merge all recent trunk enhancements into the reuse-schema branch. (check-in: e469b022 user: drh tags: reuse-schema) | |
| 10:45 | Merge all recent trunk enhancements into the bedrock branch. (check-in: 33d3453f user: drh tags: bedrock) | |
| 10:42 | Merge all recent trunk enhancements into the wal2 branch. (check-in: c2139d82 user: drh tags: wal2) | |
| 10:42 | Merge all recent trunk enhancements into the begin-concurrent branch. (check-in: 9b854e54 user: drh tags: begin-concurrent) | |
|
2024-03-25
| ||
| 20:35 | The RAISE() operator is not a constant expression and cannot participate in the VALUE-as-coroutine optimization. dbsqlfuzz 74cf7c9904360322a6c917e4934b127543d1cd51 (check-in: 6a06dc73 user: drh tags: trunk) | |
| 20:00 | Add further tests for sqlite3_declare_vtab(). (check-in: f3c4433f user: dan tags: trunk) | |
| 19:31 | Simplifications to the sqlite3_declare_vtab() implementation. Changes some conditionals into assert() statements, for coverage. (check-in: ff7b898a user: drh tags: trunk) | |
| 18:30 | Fix a theoretical OOB memory access in sqlite3_stmt_scanstatus_v2(). (check-in: 87be9580 user: dan tags: trunk) | |
| 18:24 | Revert the previous change. Instead, do a pre-check of the CREATE TABLE statement that is the second argument to sqlite3_declare_vtab() and if the first two keywords are not "CREATE" and "TABLE", then raise an SQLITE_MISUSE error. (check-in: 6a2ff835 user: drh tags: trunk) | |
| 17:43 | Remove an ALWAYS() from a condition that can be true. (check-in: 715fcf03 user: drh tags: trunk) | |
| 14:44 | Fix an inaccuracy in automatic indexes that was exposed by the fix at [80c4223098c1827f]. (check-in: fdc9406f user: drh tags: trunk) | |
| 13:18 | Fix the pragma4.test script so that it works with SQLITE_OMIT_VIRTUALTABLE. (check-in: f8fe6fb6 user: drh tags: trunk) | |
| 12:28 | Fix recent test case changes so that they also work on Windows. (check-in: 38578b5a user: drh tags: trunk) | |
| 11:34 | Use the SQLITE_CONSTRAINT return value from xBestIndex to prohibit bad query plans in the pragma virtual table. (check-in: b1259d44 user: drh tags: trunk) | |
| 10:55 | Improvements to the vtablog.c extension: Eliminate memory leaks. More diagnostic output for xBestIndex. (check-in: 92e9a71b user: drh tags: trunk) | |
| 10:28 | Flag sqlite3_trace() and sqlite3_profile() as deprecated so that the doc generator for funclist.html sees them as such, and add 'Deprecated' to their page's title for consistency with other deprecated APIs. Comment changes only. Addresses forum post 0901025836. (check-in: 87c54f93 user: stephan tags: trunk) | |
| 00:38 | Improvements to the vtablog.c extension, for better logging of virtual table interactions. (check-in: e253bb36 user: drh tags: trunk) | |
|
2024-03-24
| ||
| 21:18 | Fix the xBestIndex method of the pragma virtual table so that it correctly gives a higher cost to plans where the schema hidden parameter is unconstrained. (check-in: ec791413 user: drh tags: branch-3.45) | |
| 21:15 | Fix the xBestIndex method of the pragma virtual table so that it correctly gives a higher cost to plans where the schema hidden parameter is unconstrained. (check-in: d68fb8b5 user: drh tags: branch-3.44) | |
| 21:10 | Fix the xBestIndex method of the pragma virtual table so that it correctly gives a higher cost to plans where the schema hidden parameter is unconstrained. Fix for the problem reported by forum post 85b6a8b6705fb77a. (check-in: bc516ff5 user: drh tags: trunk) | |
| 20:26 | Improved "wheretrace" debugging output for calls to xBestIndex. No changes to release code. (check-in: 33966bb0 user: drh tags: trunk) | |
| 19:08 | Fix the SQLITE_ALLOW_ROWID_IN_VIEW bug-compatibility option so that it works again. Add the SQLITE_CONFIG_ROWID_IN_VIEW sqlite3_config() value to optionally disable the bug-compatibility mode at start-time. Enable testing of SQLITE_ALLOW_ROWID_IN_VIEW. (check-in: 7a3d0027 user: drh tags: branch-3.45) | |
| 16:42 | Do not automatically assume that ROWID is NOT NULL when compiled with SQLITE_ALLOW_ROWID_IN_VIEW. dbsqlfuzz 31b38eeb63a4e1562de665078f52b7b47a7543cf (check-in: b5d2dce1 user: drh tags: branch-3.44) | |
| 16:33 | Do not automatically assume that ROWID is NOT NULL when compiled with SQLITE_ALLOW_ROWID_IN_VIEW. dbsqlfuzz 31b38eeb63a4e1562de665078f52b7b47a7543cf (check-in: 80c42230 user: drh tags: trunk) | |
|
2024-03-23
| ||
| 15:17 | Fix an adverse interaction between CREATE TABLE AS and the new VALUES-as-coroutine optimization. dbsqlfuzz c2c5e7e08b7e489d270a26d895077a03f678c33b (check-in: 84b6fdea user: drh tags: trunk) | |
|
2024-03-22
| ||
| 10:32 | Fix incorrect boundary assert()s on the new OP_IfSizeBetween opcode. (check-in: 8eda4797 user: drh tags: trunk) | |
|
2024-03-21
| ||
| 22:18 | Test case for the assert() problem fixed by [9ba3cff9d48fe8fc]. (check-in: 865f0de7 user: drh tags: trunk) | |
| 22:12 | Fix a assert() that is incorrect, though harmless. Also add a test case. (check-in: 90537ce0 user: drh tags: branch-3.45) | |
| 22:08 | Fix a assert() that is incorrect, though harmless. Also add a test case. (check-in: 57b0c984 user: drh tags: branch-3.44) | |
| 15:52 | Add comments (only, no code) to the JS sqlite3_config() bindings reminding us why SQLITE_CONFIG_ROWID_IN_VIEW is specifically not included. JNI does not need this treatment because it explicitly supports only a very small subset of config options. (check-in: 4fea3962 user: stephan tags: trunk) | |
| 11:46 | Enhancements to testrunner.tcl: (1) Add the "--config CONFIGS" option, to that only configuration named on the comma-separated list CONFIGS are run. (2) Add the "--omit CONFIGS" to omit configuration on the CONFIGS list (3) Add the Android configuration to "release" (check-in: 4ccb3729 user: drh tags: trunk) | |
| 11:37 | Have os_unix.c reuse cached file-descriptors in the case when a read-write fd is requested on a read-only file and a read-only fd returned. (check-in: a678e854 user: dan tags: trunk) | |
| 10:35 | Fix all test cases so that they work with SQLITE_ALLOW_ROWID_IN_VIEW. (check-in: 66c69e2f user: drh tags: trunk) | |
|
2024-03-20
| ||
| 16:56 | Change EXPLAIN QUERY PLAN output to say "USE TEMP B-TREE FOR LAST TERM OF ORDER BY", or "LAST N TERMS OF ORDER BY", instead of "RIGHT PART OF ORDER BY". (check-in: 7e13a2c7 user: dan tags: trunk) | |
| 16:29 | Fix test cases for rtree and fts5. No changes to code. (check-in: 633dca90 user: drh tags: branch-3.44) | |
| 16:27 | Change EXPLAIN QUERY PLAN output to say "USE TEMP B-TREE FOR LAST TERM OF ORDER BY", or "LAST N TERMS OF ORDER BY", instead of "RIGHT PART OF ORDER BY". (Closed-Leaf check-in: cd547c50 user: dan tags: eqp-orderby) | |
| 16:04 | Have rtree avoid keeping a blob handle open following an error. (check-in: 1303716a user: drh tags: branch-3.44) | |
| 15:26 | Following a ROLLBACK that reverts changes to an RTREE, any pending queries against that same RTREE abort with code SQLITE_ABORT_ROLLBACK. dbsqlfuzz de7d17b72d0e842352c998dd86a47b7d0f707be9. (check-in: b26e5a50 user: drh tags: branch-3.44) | |
| 12:19 | Back port various minor patches (check-in: a1a5c427 user: drh tags: branch-3.44) | |
| 11:36 | Automatically disable the DISTINCT optimization during query planning if the ORDER BY clause exceeds 63 terms. dbsqlfuzz afd1d61fc27d14938a0d78a50970fa1e9fbfee58. (check-in: e8d5caef user: drh tags: branch-3.44) | |
| 11:30 | Ignore COLLATE operators when determining whether the result of a subexpression should be shallow-copied or deep-copied. (check-in: dd58d117 user: drh tags: branch-3.44) | |
| 11:25 | Fix a harmless compiler warning in the randomjson.c extension. (check-in: a4c93512 user: drh tags: branch-3.44) | |
| 11:24 | If a term of an ORDER BY or GROUP BY contains an aggregate function or column, then it is not an alias that needs to be resolved, so don't try to. This fixes a harmless assertion found by dbsqlfuzz. (check-in: e7ba2af5 user: drh tags: branch-3.44) | |
| 11:04 | Fix the SQLITE_ALLOW_ROWID_IN_VIEW bug-compatibility option so that it works again. Add the SQLITE_CONFIG_ROWID_IN_VIEW sqlite3_config() value to optionally disable the bug-compatibility mode at start-time. Enable testing of SQLITE_ALLOW_ROWID_IN_VIEW. (check-in: acc08353 user: drh tags: branch-3.44) | |
| 10:45 | Fix the SQLITE_ALLOW_ROWID_IN_VIEW bug-compatibility option so that it works again. Add the SQLITE_CONFIG_ROWID_IN_VIEW sqlite3_config() value to optionally disable the bug-compatibility mode at start-time. Enable testing of SQLITE_ALLOW_ROWID_IN_VIEW. (check-in: b6802565 user: drh tags: trunk) | |
| 10:40 | Fix a typo in a comment. (Closed-Leaf check-in: 54680d0f user: drh tags: rowid-in-view) | |
| 09:45 | Fix typos in the SQLITE_CONFIG_ROWID_IN_VIEW documentation. (check-in: 1ad1ca49 user: drh tags: rowid-in-view) | |
|
2024-03-19
| ||
| 23:01 | Change the SQLITE_CONFIG_NO_ROWID_IN_VIEW configuration option to be just SQLITE_CONFIG_ROWID_IN_VIEW (without the "_NO_" in the middle) and give it the ability to turn the option on and off. Otherwise, it is difficult to test. (check-in: 5d412edc user: drh tags: rowid-in-view) | |
| 19:56 | Return the error "ambiguous column name: rowid", instead of "no such column: rowid", when a "rowid" reference is ambiguous. (check-in: 0615bdae user: drh tags: rowid-in-view) | |
| 19:48 | Add the --no-rowid-in-view option to the --help output of the CLI. (check-in: 134da9c3 user: drh tags: rowid-in-view) | |
| 19:42 | Make sure the new u1.nRow value is copied when making a copy of a SrcItem object. This fixes a problem in [ac6f095e13e43d66] from yesterady. (check-in: 262f8f9d user: drh tags: trunk) | |
| 16:51 | Update test scripts to account for [8fcea4cd]. (check-in: 0c543c51 user: dan tags: rowid-in-view) | |
| 16:34 | In the name resolver when SQLITE_ALLOW_ROWID_IN_INDEX is enabled, if there are multiple views that might resolve to the "rowid" but only one real table, then use that one real table and ignore the views. (check-in: 8fcea4cd user: drh tags: rowid-in-view) | |
| 15:27 | Update tests to work with SQLITE_ALLOW_ROWID_IN_VIEW. (check-in: 495b8c7b user: dan tags: rowid-in-view) | |
| 14:55 | Return the error "ambiguous column name: rowid", instead of "no such column: rowid", when a "rowid" reference is ambiguous. (Closed-Leaf check-in: 021f34fc user: dan tags: ambiguous-rowid-error) | |
| 14:38 | Fix the fuzzinvariants.c test module so that it does not generate invariants that depend on rowid when SQLITE_ALLOW_ROWID_IN_VIEW is used, since rowid values can be unreliable in that context. (check-in: 0d711aaa user: drh tags: rowid-in-view) | |
| 14:21 | Improvements to the first check-in on this branch, causing less collateral damage. (check-in: 7bc88289 user: drh tags: rowid-in-view) | |
| 13:55 | On second thought, change SQLITE_TESTCTRL_ROWID_IN_VIEW into a start-time option SQLITE_CONFIG_NO_ROWID_IN_VIEW. (check-in: b8e045c9 user: drh tags: rowid-in-view) | |
| 13:31 | When compiled with SQLITE_ALLOW_ROWID_IN_VIEW, rowid-in-view is on by default but can now be turned off using SQLITE_TESTCTRL_ROWID_IN_VIEW. Without the compile-time option, rowid-in-view is always off. (check-in: 8a6196ab user: drh tags: rowid-in-view) | |
| 10:58 | Fix a problem involving infinities int the Kahan-Babushka-Neumaier summation algorithm. (check-in: 8af58781 user: drh tags: branch-3.45) | |
| 10:46 | Fix a problem involving infinities int the Kahan-Babushka-Neumaier summation algorithm. (check-in: 0984e5cd user: drh tags: branch-3.44) | |
| 10:41 | Adjustments to the test cases for the previous check-in to make them cross-platform Linux/Mac/Windows. Test changes only. No change to core code. (check-in: 0dddadbd user: drh tags: trunk) | |
| 10:16 | Fix another problem from [c63e26e705f5e967] involving infinities and the Kahan-Babushka-Neumaier summation algorithm. Problem reported by forum post 23b8688ef4. (check-in: 45d272ef user: drh tags: trunk) | |
| 02:30 | First steps toward getting -DSQLITE_ALLOW_ROWID_IN_VIEW to work again. That compile-time option is untested, undocumented, and unsupported. But it was mentioned in the release notes for version 3.36.0, so I think that means we need to support it forever. (check-in: 7c46ff64 user: drh tags: rowid-in-view) | |
|
2024-03-18
| ||
| 21:08 | Fix asan problems in sqlite3rbu.c. Enable RBU for sanitizer release tests. (check-in: ad2ae771 user: dan tags: trunk) | |
| 20:52 | Avoid spurious SQLITE_IOERR_DATA errors when reading partial pages from a cksumvfs database using a SQLITE_DIRECT_OVERFLOW_READ build. (check-in: 0f485dbe user: dan tags: trunk) | |
| 18:56 | Merge the latest trunk enhancements into the reuse-schema branch. (check-in: c2d4adab user: drh tags: reuse-schema) | |
| 18:55 | Merge the latest trunk enhancements into the bedrock branch. (check-in: 10ab5e85 user: drh tags: bedrock) | |
| 18:51 | Merge the latest trunk enhancements into the wal2 branch. (check-in: c0af1242 user: drh tags: wal2) | |
| 18:47 | Merge the latest trunk enhancements into the begin-concurrent branch. (check-in: 50b43b02 user: drh tags: begin-concurrent) | |
| 18:03 | Remove unnecessary blank lines from build commands in the default Makefile.in. (check-in: 76fb3a90 user: drh tags: trunk) | |
| 18:00 | Add the "VALUES-as-coroutine" optimization. Large VALUES clauses on an INSERT, for example, prepare and run in about half the time and with half the memory. This check-in also includes enhancements to the internal sqlite3ExprIsConstant() routine to recognize pure SQL functions as constant if they have constant arguments. (check-in: a120c923 user: drh tags: trunk) | |
| 17:13 | Fix harmless compiler (scan-build) warnings. (Closed-Leaf check-in: c86f9f2a user: drh tags: exp-values-clause2) | |
| 16:30 | Allow the VALUES-as-coroutine optimization to be applied to later rows of a VALUES clause even if earlier rows do not qualify. (check-in: 9a47ea7f user: drh tags: exp-values-clause2) | |
| 15:10 | Change a test case to use a window function rather than random() to disable the VALUES clause optimization. (check-in: c589149a user: drh tags: exp-values-clause2) | |
| 13:31 | Add assert() statements to validate access to the SrcItem.u1.nRow union member. (check-in: 21f616d9 user: drh tags: exp-values-clause2) | |
| 13:10 | Fix the patch at [10ee6fcba08ab128] so that it works on reduced-size Expr nodes. (check-in: 260bd764 user: drh tags: exp-values-clause2) | |
| 12:49 | Improvements to EXPLAIN QUERY PLAN output for multi-row VALUES claues. (check-in: ac6f095e user: drh tags: exp-values-clause2) | |
| 11:12 | Ensure the database schema has been loaded and the database encoding gleaned before beginning to code a multi-row VALUES clause. (check-in: 2ff476eb user: dan tags: exp-values-clause2) | |
| 10:54 | Fix a problem caused by a non-aggregate function with an OVER clause in a multi-row VALUES clause. (check-in: 10ee6fcb user: dan tags: exp-values-clause2) | |