David Jones

I added a kit for a new virtual table extension, pdbvtab. This kit lets you join your systems product database with VSI Service Portal package lists using relational database type queries. sqlite> select * from history where vms$cvtime(date) > '2025-07-01'; ╭────────────────┬───────────┬───────────┬──────────┬────────────────────────────┬──────────────────────╮ │ name │ installed │ available │ kit_type │ pkg_spec │ date │ ╞════════════════╪═══════════╪═══════════╪══════════╪════════════════════════════╪══════════════════════╡...

I added kit 59 to the files area, incorporating version 3.53.2 of SQLite. I added a new feature to the VFS, the appext extension, that you can enable by setting bit 5 in the auto_extension_mask. The extension checks if the database has an application ID (https://www.sqlite.org/pragma.html#pragma_application_id) set and if so uses the value to locate one or more extensions to automatically load when the file is opened. For example, a database file that depends upon the xlsx virtual table extension...

I added kit 59 to the files area, incorporating version 3.53.2 of SQLite. I added a new feature to the VFS, the appext extension, that you can enable by setting bit 5 in the auto_extension_mask. The extension checks if the database has an application ID ([application_id]https://www.sqlite.org/pragma.html#pragma_application_id) set and if so uses the value to locate one or more extensions to automatically load when the file is opened. For example, a database file that depends upon the xlsx virtual...

I added kit 59 to the files area, incorporating version 3.53.2 of SQLite. I added a new feature to the VFS, the appext extension, that you can enable by setting bit 5 in the auto_extension_mask. The extension checks if the database has an application ID ([https://www.sqlite.org/pragma.html#pragma_application_id]) set and if so uses the value to locate one or more extensions to automatically load when the file is opened. For example, a database file that depends upon the xlsx virtual table extension...

I added kit 59 to the files area, incorporating version 3.53.2 of SQLite. I added a new feature to the VFS, the appext extension, that you can enable by setting bit 5 in the auto_extension_mask. The extension checks if the database has an application ID (https://www.sqlite.org/pragma.html#pragma_application_id) set and if so uses the value to locate one or more extensions to automatically load when the file is opened. For example, a database file that depends upon the xlsx virtual table extension...

I added an incremental, vmsvfs_inc20260518.zip, to the files area. The update makes some refinements to the utf-8 conversion support: Refactored the conversion routine to use a hash table to cache translations. With 3.53.x, the shell's default output mode is qbox, so the cache will usually end up with at least a dozen or so translations for unicode box drawing characters to DSG. Fix the problem where starting the shell with the in-memory database (":memory") wasn't initializing the UTF-8 conversion...

I added an incremental, vmsvfs_inc20260518.zip, to the files area. The update makes some refinements to the utf-8 conversion support: Refactored the conversion routine to use a hash table to cache translations. With 3.53.x, the shell's default output mode is qbox, so the cache will usually end up with at least a dozen or so translations for unicode box drawing characters to DGS. Fix the problem where starting the shell with the in-memory database (":memory") wasn't initializing the UTF-8 conversion...

Added kit 58 to files area: Update to SQLite 3.53.1. Replace source_patch.c with refactored version, source_patch2.c. Patch files for the new program have a different format. Old patch files were converted to os_unix.patch2 and pragma.patch2. Replace vms_shell.c with a new program shell-vms.c, generated from the SQLite distribution's shell.c and shell.patch2. The patch technique lets us more cleanly make sqlite3_format_query_result() an external function and produce a less cluttered listing file...