Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
50 check-ins occurring around bd87d107fe474cee.
|
2022-06-25
| ||
| 07:42 | wasm: eliminated the need for Stmt objects to keep ahold of memory allocated for bound strings and blobs. Added alternate string/blob bind impls which are hypothetically more efficient but not yet proven to be so. (check-in: da1d3151a4 user: stephan tags: wasm-cleanups) | |
| 06:46 | wasm: eliminated the dependency on the deprecated emcc-provided allocate() function. Adjacent cleanups in blob binding. (check-in: 140618b212 user: stephan tags: wasm-cleanups) | |
| 03:53 | wasm: corrected the propagation of text/blob values via UDFs. DB.exec()'s sql may now be an array of strings which get concatenated together before passing it on to sqlite3_prepare_v2(). DB.exec()'s callback now applies to the first statement which has result columns instead of only the first statement. Fixed a precedence but which caused isInt32() to report false positives. (check-in: 37a8fecb56 user: stephan tags: wasm-cleanups) | |
| 02:54 | Minor wasm doc tweaks. (check-in: 42dc500819 user: stephan tags: wasm-cleanups) | |
| 02:39 | Change a harmless assert() into a testcase(). The actually test case code is in TH3. Fix for the problem described at forum post ed29e196d5c4f3d5. (check-in: cd6254fcd3 user: drh tags: trunk) | |
| 02:37 | wasm binding: consolidated the two sqlite3_prepare_v2() bindings behind a single dispathcer. Various internal cleanups and refactoring. Branched because trunk is in pencils-down mode for pending 3.39 release. (check-in: ab3e50dab4 user: stephan tags: wasm-cleanups) | |
|
2022-06-24
| ||
| 16:15 | Merge the 3.39.0 release candidate 1 changes into the reuse-schema branch. (check-in: 506a3e6f24 user: drh tags: reuse-schema) | |
| 15:26 | Merge the latest changes into the begin-concurrent-pnu-wal2 branch. (check-in: d3fa692179 user: drh tags: begin-concurrent-pnu-wal2) | |
| 15:15 | Merge 3.39.0 release candidate 1 into the wal2 branch. (check-in: 5a5e6e368f user: drh tags: wal2) | |
| 15:04 | Merge the version 3.39.0 release candidate 1 changes into the begin-concurrent-report branch. (check-in: 1b28ad2caa user: drh tags: begin-concurrent-report) | |
| 14:55 | Merge 3.39.0 release candidate 1 changes into the begin-concurrent branch. (check-in: 5ae706a401 user: drh tags: begin-concurrent) | |
| 12:56 | Fix a harmless UBSAN warning associated with PRAGMA schema_version found by OSSFuzz. (check-in: e93fd170ce user: drh tags: trunk) | |
| 11:05 | In sqlite3WhereBegin, do not proceed with coding the loop if an error is detected as part of WHERE expression analysis. For for the assertion-fault described by forum post c3496cf6b1. (check-in: db5266dec6 user: dan tags: trunk) | |
| 11:02 | A minor fix to test/fuzzinvariants.c so that it works even with column names that originally contain a ':' and that are disambiguated. (check-in: 8d9b1fff9d user: drh tags: trunk) | |
|
2022-06-23
| ||
| 22:43 | New test cases for query flattening with LEFT JOIN. (Closed-Leaf check-in: 27f68e4732 user: drh tags: flatten-left-join) | |
| 20:56 | Reintroduce flattener constraint (3c), but this time make it apply only if the outer query holds a GROUP BY, not if the outer query is an aggregate. (check-in: 641dfb9182 user: drh tags: flatten-left-join) | |
| 15:15 | Add back the ability to flatten a LEFT JOIN subquery - previously removed due to ticket [cad1ab4cb7b0fc344]. (check-in: f8fe936ad4 user: drh tags: flatten-left-join) | |
| 12:36 | Minor correction to a comment. No code changes. (check-in: 5fa00959eb user: drh tags: trunk) | |
|
2022-06-22
| ||
| 18:51 | Enhance the TCL scrip that generates sqlite3-all.c so that it outputs all text in its original order. (check-in: 83ff1a28e3 user: drh tags: trunk) | |
| 18:33 | Fix requirements marks that changed due to typo fixes in the documentation. (check-in: 5247df0599 user: drh tags: trunk) | |
| 15:55 | More comment fixes. No changes to code. (check-in: 5c9133ef43 user: drh tags: trunk) | |
| 14:43 | Allow more line with on the debugging output for SrcItem elements in the parse tree. This affects debugging builds only and is a no-op for production builds. (check-in: edbe24e7fc user: drh tags: trunk) | |
| 14:25 | Additional enhancements to comments. No changes to code. (check-in: d9a320448f user: drh tags: trunk) | |
| 14:00 | Give dbtotxt an option to prepend .open --hexdb (check-in: afeee6125d user: larrybr tags: trunk) | |
| 12:54 | Fix a typo in a comment. No changes to code. (check-in: ef9de201b3 user: drh tags: trunk) | |
|
2022-06-21
| ||
| 18:38 | Disable the short-cut query planner if the NOT INDEXED modifier is used. Forum post 454d706296. (check-in: bd87d107fe user: drh tags: trunk) | |
| 13:41 | Allow a HAVING clause on any aggregate query, even if there is no GROUP BY clause. This brings SQLite into closer agreement with PostgreSQL and fixes the concern raised by forum post 1a7fea4651. (check-in: 9322a7c21f user: drh tags: trunk) | |
| 12:54 |
| |
|
2022-06-20
| ||
| 19:12 | Add an ALWAYS() macro to an always-true branch. (check-in: 364645d8fe user: drh tags: trunk) | |
| 18:26 | Do not allow FROM-clause terms on the left side of a RIGHT or FULL JOIN to be reordered. forum post 6650cd40b5634f35. This is probably more strict that necessary to get correct behavior, but for the first release that supports RIGHT/FULL JOIN it is perhaps better to be correct than fast. A less strict constraint might be to prohibit FROM-clause terms that originate on the left side of a RIGHT JOIN from crossing from the right side to the left side of a LEFT JOIN. Revisit this later. (check-in: 238453ffab user: drh tags: trunk) | |
| 17:04 | Do not allow an ON clause to references tables to its right if there is a RIGHT or FULL join anywhere in the query. Other RDBMSes prohibit this always, but SQLite must allow ON clauses to reference tables to their right for legacy compatibility, unless there is a RIGHT or FULL join someplace in the query, in which case there is no legacy to support. (check-in: e615dbe02c user: drh tags: trunk) | |
| 12:42 | The fix at [cab9b4cccd13bf0a] was incomplete, as demonstrated by forum post 57bdf2217d. This check-in should complete the fix. (check-in: fb0a23b678 user: drh tags: trunk) | |
|
2022-06-19
| ||
| 16:55 | Follow-up to check-in [0057bbb508e7662b] - ensure that the database page has been initialized prior to continuing with the optimization. If the page is not initialized, that indicates that the database is corrupt. dbsqlfuzz 09ee46becd5e6d1b2a55c9f8ad767335a90aadb0. (check-in: 11162446f1 user: drh tags: trunk) | |
|
2022-06-18
| ||
| 20:20 | Enable query invariant checking in fuzzcheck by default. There is no way to turn it off. Update the invariant checking logic to be consistant with dbsqlfuzz. (check-in: 66ca729bbb user: drh tags: trunk) | |
| 14:50 | Abandon a query-invariant check in fuzzcheck if the call to sqlite3_bind_value() returns anything other than SQLITE_OK or SQLITE_RANGE. (check-in: d31e1cd2ab user: drh tags: trunk) | |
| 10:26 | In the --query-invariants option of fuzzcheck, correctly deal with OOMs causing the return value of sqlite3_column_name() to be NULL. (check-in: eabbee4a51 user: drh tags: trunk) | |
|
2022-06-17
| ||
| 21:31 | Fix the OP_Concat operator such that when concatenating a BLOB with an odd number of bytes on a database that is UTF16, the size of the resulting string is reduced to a multiple of two. (check-in: 5eb2c23635 user: drh tags: trunk) | |
| 17:11 | Omit the --query-invariants processing in fuzzcheck for queries that contain the implies_nonnull_row() test function. (check-in: 0602a08448 user: drh tags: trunk) | |
| 16:52 | Do not run --query-invariants on statements that make use of sqlite_offset(). (check-in: c5ac4cbfb1 user: drh tags: trunk) | |
| 16:39 | Various fixes and improvements to the --query-invariants option of fuzzcheck. (check-in: 09aca89b7c user: drh tags: trunk) | |
| 16:32 | Allow integers and floating point numbers to compare equal. (Closed-Leaf check-in: 0fe2e465ba user: drh tags: query-invariants) | |
| 16:09 | Improve query-invariants to the point that it would have discovered the [f23a429d4153518d] bug if that bug had not already been fixed. (check-in: 2a7251ed9c user: drh tags: query-invariants) | |
| 15:52 | Only run query-invariant checks after the original query has run to completion, so that we know it does not error-out on a subsequent row. (check-in: d1fc857bb8 user: drh tags: query-invariants) | |
| 15:11 | Fix the virtual table detection mechanism to avoid false-positives that were blocking all failures. Then fix a few of the additional problems that are revealed by that fix. More fixes are needed. (check-in: 42b2e6676f user: drh tags: query-invariants) | |
| 12:25 | Fix the new --query-invariants option on fuzzcheck so that it does not use an unprotected sqlite3_value object as an argument to sqlite3_value_int64(). (check-in: d9f820151d user: drh tags: trunk) | |
| 11:39 | Avoid omitting the rhs of FULL JOINs in cases where it is only correct to omit the rhs of a LEFT JOIN. Fix for the problem reported by forum post 5610c17c3d. (check-in: f23a429d41 user: dan tags: trunk) | |
| 00:24 | Tiny fiddle cleanups. (Closed-Leaf check-in: 01969ba568 user: stephan tags: fiddle-indexeddb) | |
|
2022-06-16
| ||
| 23:55 | fiddle: initial proof of concept of using Emscripten's IndexedDB virtual filesystem for a persistent db. There's still much work to do to integrate this into something useful for clients but the concept is now proven. (check-in: 65c152d335 user: stephan tags: fiddle-indexeddb) | |
| 20:29 | Minor fix to the query invariant testing logic of fuzzcheck. (check-in: 447e62a094 user: drh tags: trunk) | |
| 13:57 | Merge the latest trunk enhancements into the reuse-schema branch. (check-in: 7f405fe209 user: drh tags: reuse-schema) | |