Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
58 events for the month beginning 2023-01-01 by user drh
Following month ↑|
2023-01-30
| ||
| 20:44 | Additional tweaks to the enhancement at [609fbb94b8f01d67] to further reduce the cost estimate for constructing an automatic index on an ephemeral table, in order to resolve the performance problem described by forum post 1d571c0296. (check-in: bf1aae7a user: drh tags: trunk) | |
|
2023-01-28
| ||
| 21:01 | Show more details about the SrcItem.fg field in tree-trace output. (check-in: 3d05dddd user: drh tags: trunk) | |
|
2023-01-27
| ||
| 23:10 | Fix compiler warning in base85.c. (check-in: bd9613fd user: drh tags: trunk) | |
| 20:15 | Add an assert() to help static analyzers. (check-in: e446c8b4 user: drh tags: trunk) | |
|
2023-01-26
| ||
| 02:18 | Improved fix to allow sqlite3_vtab_in_first() to reliably return SQLITE_ERROR. (check-in: b25eec1c user: drh tags: trunk) | |
|
2023-01-25
| ||
| 21:28 | Fix a harmless compiler warning in FTS3. (check-in: 68d02d3c user: drh tags: trunk) | |
| 19:05 | Defer calling the destructor for the user data on a module until after the module has disconnected. Forum post b68391eb71fdff73. (check-in: 1ab12228 user: drh tags: trunk) | |
| 16:56 | Enhance the sqlite3_vtab_in_first() and sqlite3_vtab_in_next() interfaces so that they reliably return SQLITE_ERROR (and not SQLITE_MISUSE) if they are invoked on a parameter that did not have multi-value IN processing enabled via a prior call to sqlite3_vtab_in(). See forum thread a823d4a3d5f73def. (check-in: 144326dc user: drh tags: trunk) | |
|
2023-01-23
| ||
| 21:41 | Suppress a harmless compiler warning. Forum post e3f72e9291189925. The code was legal and correct. The revised code is actually less clear in its intent. But at least now there will (hopefully) be no warning. (check-in: 48bb7c88 user: drh tags: trunk) | |
| 20:45 | Due to a coding error, check-in [8efd61e8518594e3] did not actually use just read transactions if the operation is read-only and the SQLITE_MAX_ATTACHED macro is set to 31 or more. This was due to a misuse of the writeMask field of Parse, pointed out by forum post aa173c18d5. (check-in: 87605668 user: drh tags: trunk) | |
| 16:16 | Add the missing CARRAY_BLOB macro to the carray.h extension header. (check-in: 10bf639c user: drh tags: trunk) | |
|
2023-01-21
| ||
| 00:59 | Fix a memory leak in the TCL test harness associated with carray. (check-in: 5a316f9f user: drh tags: trunk) | |
| 00:19 | Fix harmless compiler warnings. (check-in: ded60f5b user: drh tags: trunk) | |
|
2023-01-20
| ||
| 21:00 | Extend the carray extension to allow the use of BLOB values to be bound as an array of "struct iovec" objects. (check-in: e117a03c user: drh tags: trunk) | |
| 19:19 | Two branches associated with memdb are now always taken (I believe). Tag them with ALWAYS() to verify this. (check-in: 20b9b5aa user: drh tags: trunk) | |
| 13:34 | The json_group_array(), json_group_object(), and fts5_source_id() functions should all be deterministic and innocuous. (check-in: edcb83fa user: drh tags: trunk) | |
|
2023-01-17
| ||
| 19:00 | Change an now unreachable testcase() into an assert(). (check-in: 517b2c4c user: drh tags: trunk) | |
| 18:40 | Fix harmless compiler warnings in the CLI. (check-in: 7cf282d3 user: drh tags: trunk) | |
| 13:33 | Add test cases to confirm that the schema parsing quirk in which an ON CONFLICT clause is accepted and ignored on table CHECK constraints but raises an error on column CHECK constraints. We want to continue supporting this harmless quirk to avoid breaking legacy applications and databases that accidentally use it. (check-in: 92b6a9cd user: drh tags: trunk) | |
|
2023-01-16
| ||
| 18:13 | In the CLI, create our own private version of strncpy() to work around false-positive compiler warnings from Alpine Linux. (check-in: 83f21285 user: drh tags: trunk) | |
|
2023-01-14
| ||
| 19:53 | Omit the long-disused FTS1 and FTS2 implements from the active source tree. The code will persist forever in the source repository, but there is no point in carrying it around in the latest tarballs where it is never used. (check-in: 2bb50d5a user: drh tags: trunk) | |
| 19:36 | Add OOM check, per tip at forum post 933479b2d5 (Leaf check-in: c66c7734 user: drh tags: branch-3.40) | |
|
2023-01-13
| ||
| 19:32 | In expression nodes of type REGISTER with sub-type COLUMN, ensure that the iColumn field is set correctly, as otherwise the "IS NULL" operator might be incorrectly optimized. Fix for the problem described by forum post d010a26798915b53. (check-in: 76b440c5 user: drh tags: branch-3.40) | |
| 19:29 | In expression nodes of type REGISTER with sub-type COLUMN, ensure that the iColumn field is set correctly, as otherwise the "IS NULL" operator might be incorrectly optimized. Fix for the problem described by forum post d010a26798915b53. (check-in: 0819a186 user: drh tags: trunk) | |
| 19:00 | Fix an error in debugging output discovered while working on the problem with RETURNING reported by forum post d010a26798. (Leaf check-in: 3ae9127f user: drh tags: returning-is-null-fix) | |
| 18:20 | Add missing "const" on variables in recent RBU fixes. (check-in: 9b8dcd79 user: drh tags: trunk) | |
| 15:54 | Enhance query planning so that it check for sqlite3_interrupt() calls and periodically invokes the progress handler callback (if any) during long query analyses. (check-in: bd8fa10e user: drh tags: trunk) | |
| 15:31 | Update documentation for sqlite3_progress_handler(). (Closed-Leaf check-in: 41b4c407 user: drh tags: progress-during-prepare) | |
| 11:31 | Remove an incorrect legacy assert(). (check-in: 3006b3b3 user: drh tags: progress-during-prepare) | |
|
2023-01-12
| ||
| 20:36 | Reduce the frequency of calls to sqlite3ProgressCheck(). (check-in: 795aca4a user: drh tags: progress-during-prepare) | |
| 19:51 | Fix sqlite3_prepare() so that it only invokes the progress handler on every N-th call to sqlite3ProgressCheck(), where N is the progress handler step count. Also fix faulty asserts exposed by the ability to interrupt in the middle of sqlite3_prepare(). (check-in: 05461651 user: drh tags: progress-during-prepare) | |
| 13:25 | Attempt to provide a mechanism to do early termination of long-running statement preparation by invoking the progress handler at strategic points during sqlite3_parpare(). This experiment shows that sqlite3_prepare() might leave the resulting prepared statement uninitialized following an interrupt. (check-in: 79636f2d user: drh tags: progress-during-prepare) | |
|
2023-01-11
| ||
| 20:52 | Fix duplicate semicolon in btreeInt.h. Forum post 8db1711ca2 (check-in: 7526c466 user: drh tags: trunk) | |
| 17:59 | Fix a false-positive in the out-of-range jump detection logic that was added as part of RIGHT JOIN. (check-in: ab5bcb91 user: drh tags: trunk) | |
| 17:50 | If OP_Rewind has P2 of zero, that is an assertion that the table is never empty. This fixes a false-positive in the out-of-subroutine jump detection logic added in version 3.39.0, and which was causing the assertion on the previous check-in. (Closed-Leaf check-in: 33fd9997 user: drh tags: code-generator-20230111) | |
| 16:48 | • Edit [b8f994414285264f|b8f99441]: Move to branch code-generator-20230111. (artifact: 6dd8ac05 user: drh) | |
| 16:44 | Add an assert() to the byte-code engine that goes off if the OP_Halt opcode is invoked with SQLITE_INTERNAL. This causes the RIGHT JOIN error "Opcode jumps to ... which is outside the subroutine ..." to fail immediately, causing it to come more readily to tester's attention. There is at least one testcase in test/fuzzdata8.db that asserts due to this change. (check-in: b8f99441 user: drh tags: code-generator-20230111) | |
| 16:17 | Improved progress-handler and interrupt detection during PRAGMA integrity_check. (check-in: 6db42780 user: drh tags: trunk) | |
| 00:27 | Add a new sqlite3_is_interrupted() interface that can be used by long-running app-defined functions and similar to see if they need to exit early due to an sqlite3_interrupt() call. (check-in: d030f341 user: drh tags: trunk) | |
|
2023-01-10
| ||
| 19:57 | When computing the datatypes for columns in a view, use the same datatype name as the underlying table if such is available and is consistent with the computed affinity of the column. Forum thread 7fb1fe9dcf310ef5. (check-in: 497a9836 user: drh tags: trunk) | |
| 15:09 | • Edit [b829dd1b97645461|b829dd1b]: Edit check-in comment. (artifact: 3979338c user: drh) | |
| 14:33 | Improvements to the SQLITE_DIRECTONLY documentation. (check-in: b277ba40 user: drh tags: trunk) | |
|
2023-01-09
| ||
| 12:01 | Fix JSON functions so that they work correctly under PRAGMA trusted_schema. Forum thread c88a671ad083d153. (check-in: 51a5d83c user: drh tags: trunk) | |
|
2023-01-07
| ||
| 21:03 | • Edit [863c03bee117e81b|863c03be]: Edit check-in comment. (artifact: e73de900 user: drh) | |
| 21:02 | • Edit [e4de5777578d27ae|e4de5777]: Edit check-in comment. (artifact: 2d142499 user: drh) | |
| 21:02 | • Edit [d32757ddf5d311b6|d32757dd]: Edit check-in comment. (artifact: a00ff893 user: drh) | |
|
2023-01-05
| ||
| 14:41 | Changes a testcase() into an assert() due to the [e58bba93717cd6ff] change. (check-in: a6251d72 user: drh tags: trunk) | |
| 13:55 | Remove the unused sqlite3IsMemdb() routine, to avoid a harmless compiler warning. (check-in: 4f512a39 user: drh tags: branch-3.40) | |
| 13:41 | Fix a problem with applying integer affinity to a MEM_IntReal value. Forum post d270125fae. (check-in: d28d9398 user: drh tags: branch-3.40) | |
| 01:32 | Increase the version number to 3.40.2. (check-in: 43375ef8 user: drh tags: branch-3.40) | |
| 01:29 | In the zipfile extension (which is not part of the SQLite amalgamation, but which is included in the CLI by default) ensure that fopen() is not invoked using a NULL filename. Fix for the issue reported by forum post d1c96a9032e564f8. (check-in: e4de5777 user: drh tags: branch-3.40) | |
| 01:26 | In the zipfile extension (which is not part of the SQLite amalgamation, but which is included in the CLI by default) ensure that fopen() is not invoked using a NULL filename. Fix for the issue reported by forum post d1c96a9032e564f8. (check-in: d32757dd user: drh tags: trunk) | |
|
2023-01-04
| ||
| 18:32 | Adjustments to the tool/warnings.sh script to account for compiler differences. (check-in: 863c03be user: drh tags: trunk) | |
| 15:18 | Enhance PRAGMA integrity_check so that it verifies that the string values stored in indexes are byte-for-byte identical to the values in the table, and not just equivalent according to the collating sequence. dbsqlfuzz 686e2e205e0c0594d3fb524bea0c25e621d1a870. (check-in: 9302e4bf user: drh tags: trunk) | |
| 11:58 | Remove the unused "sqlite3StackAllocZero()" macro. (check-in: f0ca5720 user: drh tags: trunk) | |
|
2023-01-03
| ||
| 19:27 | Small performance increase in the symbol hash table. (check-in: a19597b4 user: drh tags: trunk) | |
| 18:51 | Avoid an unnecessary call to strlen() in the sqlite3VdbeMemStringify() routine, for a performance increase and size reduction. (check-in: 284382d3 user: drh tags: trunk) | |
| 15:11 | Small performance improvement in the btreeOverwriteCell() routine. (check-in: df5ea471 user: drh tags: trunk) | |