Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
100 most recent check-ins
|
2022-01-28
| ||
| 23:44 | Add the SQLITE_INDEX_CONSTRAINT_LIMIT and SQLITE_INDEX_CONSTRAINT_OFFSET constraints to the sqlite3_index_info for the xBestIndex method of virtual tables. (Leaf check-in: 1e227ad9 user: drh tags: trunk) | |
| 23:19 | Add a NEVER() on an unreachable branch. (Closed-Leaf check-in: 38892625 user: drh tags: vtab-limit-offset) | |
| 21:39 | When nesting Parse objects, make sure the new one has nErr set if there has been an OOM error. (check-in: ae088cbc user: drh tags: trunk) | |
| 19:53 | Include hidden columns of table valued functions that are constrained by the function arguments in the colUsed bitmask. (check-in: 8f8cab0d user: drh tags: vtab-limit-offset) | |
| 18:43 | Remove a NEVER() that has become reachable now that we have the sqlite3_vtab_rhs_value() interface. (check-in: c4c30df7 user: drh tags: vtab-limit-offset) | |
| 13:18 | Enable SQLITE_INDEX_CONSTRAINT_LIMIT/OFFSET even if there are vector comparison operators in the WHERE clause. Also: Do not enable sqlite3_vtab_rhs_value() for LIMIT/OFFSET if the value is negative, as this violates an invariant on Expr.u.iValue. (check-in: 140480b3 user: drh tags: vtab-limit-offset) | |
|
2022-01-27
| ||
| 21:18 | Query planner always honors the aConstraintUsage[].omit flag for the SQLITE_INDEX_CONSTRAINT_OFFSET constraint. (check-in: 38c5151e user: drh tags: vtab-limit-offset) | |
| 18:45 | Make LIMIT and OFFSET values available to sqlite3_vtab_rhs_value(). (check-in: b2d37c08 user: drh tags: vtab-limit-offset) | |
| 16:14 | Give the virtual table xBestIndex method access to (some) OFFSET and LIMIT clauses. (check-in: 74fa5757 user: drh tags: vtab-limit-offset) | |
| 13:52 | Enforce the restriction that 'unixepoch' only works as the first modifier after the time-value. This has been documented since 2004, but has never actually been enforced before. Also add new test cases for date/time functions with evidence marks. (check-in: 64fa9e8c user: drh tags: trunk) | |
|
2022-01-25
| ||
| 16:28 | Merge the latest trunk enhancements into the reuse-schema branch. (Leaf check-in: 6e4154d4 user: drh tags: reuse-schema) | |
| 16:05 | Merge the latest trunk changes into begin-concurrent-pnu-wal2 (Leaf check-in: 3d949775 user: drh tags: begin-concurrent-pnu-wal2) | |
| 15:57 | Merge the latest trunk changes into the wal2 branch. (Leaf check-in: 84f737ab user: drh tags: wal2) | |
| 15:48 | Merge the latest trunk enhancements into the begin-concurrent-report branch. (Leaf check-in: 42e6d842 user: drh tags: begin-concurrent-report) | |
| 15:20 | Merge the latest trunk enhancements into the begin-concurrent branch. (Leaf check-in: dae81f45 user: drh tags: begin-concurrent) | |
| 00:03 | Minor adjustment to error handling in sqlite3FinishCoding(). (check-in: a8db6941 user: drh tags: trunk) | |
|
2022-01-24
| ||
| 21:47 | Remove an unnecessary assert() that is sometimes not true following an OOM. (check-in: e9361d72 user: drh tags: trunk) | |
| 20:20 | New dbsqlfuzz cases added to test/fuzzdata8.db. (check-in: d1fbf633 user: drh tags: trunk) | |
| 20:16 | One of the ALWAYS() macros in the previous check-in could sometimes be false, following an OOM. Remove it. Problem found by dbsqlfuzz. (check-in: 11df9187 user: drh tags: trunk) | |
| 19:38 | Add ALWAYS() macros. Change some existing ALWAYS() into assert(). Other code simplifications. (check-in: 4aa27b4f user: drh tags: trunk) | |
| 16:47 | Remove many redundant checks for sqlite3.mallocFailed now that any OOM should cause Parse.nErr to be non-zero. (check-in: 1f7fa461 user: drh tags: trunk) | |
| 15:34 | Make it so that any Parse object is always linked into the database conenction while it is active. Hence, an OOM will cause Parse.nErr to be set. (check-in: 6a45d8fe user: drh tags: trunk) | |
| 14:01 | Fix testcase for CLI .read recursion. (check-in: 53d44044 user: larrybr tags: trunk) | |
| 12:48 | Make sure the sqlite3OomFault() routine sets an error in the Parse object if there is a Parse object active and linked to the database connection. (check-in: ad7aace7 user: drh tags: trunk) | |
| 11:25 | Ensure that any error encountered while coding a trigger program is transfered to the main Parse structure before it is used with any other routine that might set the error code. (check-in: 42936565 user: dan tags: trunk) | |
| 07:11 | Take CLI input redirect recursion limit from trunk (Leaf check-in: 5e702044 user: larrybr tags: shell-tweaks) | |
| 06:36 | Limit CLI input redirect nesting (check-in: 7a073931 user: larrybr tags: trunk) | |
| 04:21 | Add CLI .x command, make string redirection work (check-in: 2f2f1aae user: larrybr tags: shell-tweaks) | |
| 00:22 | CLI prepared for reading string input (check-in: 073ded4d user: larrybr tags: shell-tweaks) | |
|
2022-01-23
| ||
| 20:54 | Factor out DB protection lift and restore in CLI (check-in: 4462ed89 user: larrybr tags: shell-tweaks) | |
| 04:19 | Shell refinements, seeargs, booleans, undocumented commands (check-in: 8735caf1 user: larrybr tags: shell-tweaks) | |
| 02:53 | Create new branch named "shell-tweaks" (check-in: 3f13df29 user: larrybr tags: shell-tweaks) | |
|
2022-01-22
| ||
| 22:28 | Add support for the sqlite3_vtab_distinct() interface. Virtual table implementations can use this API to determine more detail about the ordering requirements needed by the query plan and perhaps reduce the amount of work required to compute a correct answer. This is an optimization opportunity for the virtual table implementation. The correct answer should still be obtained (though perhaps more slowly) even if sqlite3_vtab_distinct() is ignored. (check-in: e4caf1e3 user: drh tags: trunk) | |
| 20:45 | Bring sqlite3_vtab_distinct() up to spec so that it works as described in the documentation. (Closed-Leaf check-in: 4289edf3 user: drh tags: sqlite3_vtab_distinct) | |
| 19:19 | Iimproved documentation for sqlite3_vtab_distinct(). No changes to code. (check-in: 7af03f02 user: drh tags: sqlite3_vtab_distinct) | |
| 02:52 | Omit the WhereLoopBuilder.pOrderBy field, which is no longer needed. (check-in: a13afc90 user: drh tags: sqlite3_vtab_distinct) | |
| 00:18 | An initial attempt to implement sqlite3_vtab_distinct(). (check-in: d571262d user: drh tags: sqlite3_vtab_distinct) | |
|
2022-01-21
| ||
| 19:26 | Update evidence marks for the latest changes to the documentation. (check-in: 19247e91 user: drh tags: trunk) | |
| 18:57 | Fix some of the new date/time function features to comply with the spec. Update requirement marks. (check-in: 2f5dc7a9 user: drh tags: trunk) | |
| 16:47 | When computing a vector to be used as a key for an index lookup, do not check for NULL values and abort until after all key values have been computed, in case one of the later key values involves some initialization that is needed by a LEFT JOIN. Fix for the problem identified by Forum post ab95010d410a0a55. (Leaf check-in: 3bc8d162 user: drh tags: branch-3.37) | |
| 16:41 | When computing a vector to be used as a key for an index lookup, do not check for NULL values and abort until after all key values have been computed, in case one of the later key values involves some initialization that is needed by a LEFT JOIN. Fix for the problem identified by Forum post ab95010d410a0a55. (check-in: 4db5217a user: drh tags: trunk) | |
| 01:00 | Add the sqlite3_vtab_rhs_value() interface, allowing the xBestIndex method of a virtual table to access known values on the right-hand side of constraint expressions. (check-in: e19a0b13 user: drh tags: trunk) | |
| 00:38 | Add requirements marks and tuning. (Closed-Leaf check-in: ac951490 user: drh tags: sqlite3_vtab_rhs_value) | |
|
2022-01-20
| ||
| 19:00 | Test cases for sqlite3_vtab_rhs_value() based on the qpvtab extension. (check-in: 577d3d66 user: drh tags: sqlite3_vtab_rhs_value) | |
| 18:27 | Enhancements to the qpvtab virtual table to make it more useful for testing and verification of virtual table interfaces. (check-in: 850efc4c user: drh tags: sqlite3_vtab_rhs_value) | |
| 17:10 | Initial implementation of the sqlite3_vtab_rhs_value() interface and the qpvtab extension used for testing the virtual table interface. (check-in: 0873c76b user: drh tags: sqlite3_vtab_rhs_value) | |
| 14:51 | A better and more robust fix for the problem of reading a read-only WAL mode database with existing -wal and -shm files, replacing [f426874e005e3c23]. (check-in: 1266220a user: drh tags: branch-3.37) | |
| 14:40 | A better and more robust fix for the problem of reading a read-only WAL mode database with existing -wal and -shm files, replacing [f426874e005e3c23]. (check-in: 71bfd0b5 user: drh tags: trunk) | |
| 12:58 | Fix harmless scan-build warnings. (check-in: ab160e8b user: drh tags: trunk) | |
| 12:36 | Fix the ability to read read-only WAL-mode database when -shm is present, ([00ec95fcd02bb415|check-in 00ec95fcd02bb415]) so that it works for the case of 64K page size. (check-in: 2cc15e2f user: drh tags: branch-3.37) | |
| 05:20 | A WIP checkin, progress toward what .help promises (Leaf check-in: 4688e6df user: larrybr tags: script_command) | |
| 02:04 | Fix the ability to read read-only WAL-mode database when -shm is present, ([00ec95fcd02bb415|check-in 00ec95fcd02bb415]) so that it works for the case of 64K page size. (check-in: f426874e user: drh tags: trunk) | |
|
2022-01-19
| ||
| 21:11 | Initial help changes for .script (and enhanced .parameter) (check-in: a94ab403 user: larrybr tags: script_command) | |
| 20:38 | Mistaken branch creation. (Closed-Leaf check-in: 03548c25 user: larrybr tags: mistake) | |
| 18:31 | Fix a test result for alterauth2.test due to the recent fix to authorizer calls for ALTER TABLE DROP COLUMN. (check-in: e799a35f user: drh tags: trunk) | |
|
2022-01-18
| ||
| 16:16 | Fix ALTER TABLE DROP COLUMN so that it invokes the authorizer. Fix for forum post fd82b85947541dec. (check-in: aca6c61d user: drh tags: trunk) | |
|
2022-01-17
| ||
| 23:53 | Allow an "IntReal" value to count as a REAL when checking types for insertion into a generated column on a STRICT table. Forum post fa012c77796d9399. (check-in: b6fb223d user: drh tags: branch-3.37) | |
| 23:37 | Allow an "IntReal" value to count as a REAL when checking types for insertion into a generated column on a STRICT table. Forum post fa012c77796d9399. (check-in: 1ec44d55 user: drh tags: trunk) | |
| 20:01 | Merge the latest trunk changes into the reuse-schema branch. (check-in: 769ff857 user: drh tags: reuse-schema) | |
| 19:46 | Merge the latest trunk enhancements into the begin-concurrent-pnu-wal2 branch. (check-in: 45fa7efe user: drh tags: begin-concurrent-pnu-wal2) | |
| 19:36 | Merge the latest trunk enhancements into the wal2 branch. (check-in: 82f031b4 user: drh tags: wal2) | |
| 19:24 | Bring the begin-concurrent-report branch up to date with all the latest trunk enhancements. (check-in: ef6fc895 user: drh tags: begin-concurrent-report) | |
| 19:17 | Merge recent trunk enhancements into the begin-concurrent branch. (check-in: 02daae7a user: drh tags: begin-concurrent) | |
| 19:10 | Merge the begin-concurrent-pnuu branch into begin-concurrent. (check-in: 22fb5050 user: drh tags: begin-concurrent) | |
| 17:22 | .ar fixed and constituent line numbers off (until they are right) (Leaf check-in: ec363f81 user: larrybr tags: cli_extension) | |
| 15:23 | Fix incorrect testcase() and assert() macros in json.c. They were not causing problems. The assert() was simply unreachable. The testcase() added an unreachable condition. (check-in: 5623497a user: drh tags: trunk) | |
| 14:42 | Never allow the b-tree layers view of the number of pages in the database file exceed the actual number of pages in the database file, even when PRAGMA writeable_schema=ON. This helps with earlier detection of corruption, and prevents excess memory usage and CPU cycles in some integrity_check ops. (check-in: 0407c879 user: drh tags: trunk) | |
| 03:53 | Merge from trunk, w/adapations. (.ar still broken) (check-in: e09a6dd7 user: larrybr tags: cli_extension) | |
| 03:25 | Bring .import --schema enhancement in. Refine mkshellc include logic. (check-in: e38f45cd user: larrybr tags: cli_extension) | |
|
2022-01-16
| ||
| 19:11 | Fix test cases so that they all still work even with -DSQLITE_DQS=0. (check-in: 48837766 user: drh tags: trunk) | |
| 15:15 | Fix ALTER TABLE so that it works even when compiled using -DSQLITE_DQS=0. Forum post 3c1a00b66fca81fe. (check-in: 092ad64f user: drh tags: trunk) | |
|
2022-01-14
| ||
| 23:28 | Remove code from lemon.c that was made superfluous by [1b22b42e59793af1|check-in 1b22b42e59793af1] in late 2017. (check-in: 6d2f95a4 user: drh tags: trunk) | |
| 21:34 | Fix a NEVER() in the byte-code engine that can sometimes be true. Test case in TH3. (check-in: 7ac91b53 user: drh tags: trunk) | |
| 16:29 | For .import schema, quote it as for other identifiers. (check-in: bff9153c user: larrybr tags: trunk) | |
|
2022-01-13
| ||
| 21:22 | Add --schema S option to .import (check-in: 38d9dbca user: larrybr tags: trunk) | |
|
2022-01-12
| ||
| 20:31 | When the result of a subquery is to be stored in a register and that subquery has an ORDER BY clause and an OFFSET, NULL out the destination register before starting the ORDER BY so that the register will be set correctly even if the OFFSET is larger than the number of output rows. Fix for the problem reported in forum post 0ec80f12d02acb3f. (check-in: 9282bcde user: drh tags: trunk) | |
| 01:42 | Make tool/mctimec.tcl effect more regular and obvious (check-in: 02aaa10f user: larrybr tags: trunk) | |
| 00:52 | Fix mkctimec.tcl with the updated compile-time options for JSON. (check-in: 8ded3f5b user: drh tags: trunk) | |
| 00:28 | Fix harmless compiler warning seen with MSVC. (check-in: adebb9d7 user: mistachkin tags: trunk) | |
|
2022-01-11
| ||
| 23:28 | Merge the JSON interface into the core. Add -> and ->> operators for JSON that are compatible with by MySQL and PG. (check-in: 4cbb3e3e user: drh tags: trunk) | |
| 22:06 | Remove vestigial traces of json_ntype(). (Closed-Leaf check-in: 8da07c8b user: drh tags: json-in-core) | |
| 18:01 | Fix the PG-compatible -> and ->> path parsing. (check-in: 22d51383 user: drh tags: json-in-core) | |
|
2022-01-10
| ||
| 17:43 | Fix typo in the json-enhancements.md document. (check-in: feba24ef user: drh tags: json-in-core) | |
| 15:43 | Implement the new PG-compliant versions of the -> and ->> operators. (check-in: 39eff3b9 user: drh tags: json-in-core) | |
| 13:55 | New proposal for -> and ->> operators. (check-in: 1108e12a user: drh tags: json-in-core) | |
|
2022-01-09
| ||
| 21:16 | Update the json-enhancements.md document to match the version in the json-in-core branch, as outside readers have linked to this branch. (Leaf check-in: 2027b3be user: drh tags: json-enhancements) | |
| 20:51 | Typo fix in doc/json-enhancements.md. (check-in: c3b01d49 user: drh tags: json-in-core) | |
| 20:42 | Update the doc/json-enhancements.md document to better explain the features of this branch. (check-in: b8ac938f user: drh tags: json-in-core) | |
| 19:44 | Do not enclude ENABLE_JSON1 in the compile-time options. (check-in: 8bf41bc5 user: drh tags: json-in-core) | |
| 19:36 | Merge trunk enhancements into the json-in-core branch. (check-in: ea755771 user: drh tags: json-in-core) | |
| 16:54 | Add a new built-in subtype() function. (check-in: a25f4ce2 user: drh tags: json-in-core) | |
|
2022-01-08
| ||
| 21:59 | mkshellc.tcl to convert #include to INCLUDE for in-tree includees (check-in: b1f3b317 user: larrybr tags: cli_extension) | |
| 21:50 | Add NEVER() macros to two branches that became unreachable due to [e199a851e316bd47]. (check-in: 71272caf user: drh tags: trunk) | |
| 21:00 | Add function format() as an alias for printf(), for compatibility with other systems. (check-in: 68bffc61 user: drh tags: trunk) | |
| 15:37 | Merge the JSON function enhancements from the json-enhancements branch into json-in-core. (check-in: e116501c user: drh tags: json-in-core) | |
| 15:05 | Improved commenting of changes in the json1.c extension. (check-in: 4d81425e user: drh tags: json-enhancements) | |
|
2022-01-07
| ||
| 18:09 | Notes on the JSON enhancement proposals. (check-in: 18160985 user: drh tags: json-enhancements) | |
| 17:26 | Reverse the meaningn of -> and ->>. ->> raises an error on invalid JSON but -> does not. This allows ->> to behave the same as PG and MySQL. (check-in: 85f81705 user: drh tags: json-enhancements) | |
| 17:14 | Change the -> operator to use json_extract(). The ->> operator continues to use json_nextract(). (check-in: b4c8a623 user: drh tags: json-enhancements) | |
| 17:08 | New json_nextract() function that works like json_extract() except that it returns NULL instead of raising an error if the first argument is not well-formed JSON. Or if the first argument is not well-formed JSON and the second argument is '$', then return the first argument quoted. The "->" and "->>" operators are converted to use json_nextract(). (check-in: dc00f528 user: drh tags: json-enhancements) | |