Many hyperlinks are disabled.
Use anonymous login
to enable hyperlinks.
18 check-ins using file src/shell.c.in version 2c904da443
2025-05-05
| ||
20:44 | Part 1 of 2(3?) of adding the -asdict flag to the db eval command of the Tcl interface, as proposed in forum post dce85c5ab9f0bc10. This is the lowest-level part but it does nothing because the higher-level part does not yet exist to activate it, a notable consequence of which is that it's untested. Rename pArray to pTgtName because the former name is now confusingly incorrect. (Leaf check-in: 003e2c9bca user: stephan tags: tcl-cw) | |
17:13 | Flesh out the break-as-null test cases to better demonstrate how it compares to the default of returning an empty string. (check-in: ad1ae76ad1 user: stephan tags: tcl-cw) | |
16:49 | Allow Tcl-defined UDFs to 'break' to result in an SQL NULL, as per suggestion in forum post 585ebac2c48f1411. (check-in: 034211985d user: stephan tags: tcl-cw) | |
15:12 | Merge trunk into cygwin-fixes branch. 'make test' failure count = 1 (delete_db-1.3.0) both before and after the merge, (Leaf check-in: 7471088197 user: stephan tags: cygwin-fixes) | |
2025-05-03
| ||
15:17 | Enhance sqlite3_rsync so that if the first attempt to invoke a copy of itself on the remote system using ssh fails, try again after augmenting the PATH. This enables sqlite3_rsync to work without the --exe option when the remote system is a Mac. (Leaf check-in: 38d4c94d8c user: drh tags: trunk) | |
10:55 | Fix a harmless redundant variable declaration in sqlite3_rsync. (check-in: f8f15eff6a user: drh tags: trunk) | |
10:49 | Addition summary results output when using -vvv on sqlite3_rsync. (check-in: c702999cfa user: drh tags: trunk) | |
10:35 | Promote the --protocol option to sqlite3_rsync from being an undocumented debug option to being a supported and user-visible option. This is sometimes needed to work around bugs in prior versions running on the remote. (check-in: 4855e04e44 user: drh tags: trunk) | |
08:17 | Enhance sqlite3_rsync (in a backwards-compatible way) so that it has the ability to send hashes for blocks of pages in addition to individual pages. By judicious use of this capability, network bandwidth requirement to sync two similar databases is reduced. (check-in: e5d87aaa8f user: drh tags: trunk) | |
07:00 | Improvements to protocol negotiation. (Closed-Leaf check-in: 4f5a06e420 user: drh tags: faster-rsync) | |
2025-05-02
| ||
23:50 | Clean up command-line parsing. Add the undocumented -protocol option for debugging. (check-in: 2a52b174e6 user: drh tags: faster-rsync) | |
22:25 | Now appears to be working. More testing needed. Refinement of the version-2 algorithm needed. (check-in: cb035181d9 user: drh tags: faster-rsync) | |
18:32 | Bug fixes. Added new debugging features to better visualize the protocol. (check-in: c703306686 user: drh tags: faster-rsync) | |
17:39 | This is the start of an experiment in getting sqlite3_rsync to use less bandwidth when the two databases are very similar, by sending hashes over blocks of pages initially, rather than over individual pages, then requesting more detail when hashes do not match. (check-in: 266b4b8f01 user: drh tags: faster-rsync) | |
11:18 | Do not allow sqlite3_rsync to convert the replica from WAL-mode into DELETE-mode, as that can disrupt existing clients on the replica side. DELETE-mode to WAL-mode conversions are allowed, however. See forum thread 6b575b66156. (check-in: 660a035b6c user: drh tags: trunk) | |
2025-05-01
| ||
18:07 | Enhance sqlite3_rsync so that, by default, it will sync non-WAL-mode database files. Add a new command-line option --wal-only that restricts the sync to WAL-mode databases only (the former default). Improve command-line option parsing so that only a single "-" is required before each option. (check-in: 4b53603fe4 user: drh tags: trunk) | |
16:07 | Allow sqlite3_rsync to work on non-WAL-mode databases, as long as the --wal-only flag is not used. (Closed-Leaf check-in: e4126dcd1e user: drh tags: rsync-non-wal-mode) | |
2025-04-30
| ||
14:37 | Fix a harmless problem in the CLI in which SQL errors that occur during the ".schema" command are properly ignored, yes still appear in the ".log" output. Forum post 42fe6520b8 (check-in: 20abf1ec10 user: drh tags: trunk) | |