sqlite-hub 1.1.2 → 1.4.0

package/README.md

@@ -1,11 +1,32 @@
 # sqlite-hub ⚡️
 
-[![SQLite Hub database overview](./frontend/assets/mockups/overview_1200.webp)](./frontend/assets/mockups/overview_1200.webp)
+[![SQLite Hub database overview](./frontend/assets/mockups/overview_1_1920.webp)](./frontend/assets/mockups/overview_1_1920.webp)
 
 A focused local-first app for browsing, editing, and querying SQLite databases.
 
 SQLite Hub is built for developers and technical users who want a clean SQLite workflow without heavy database clients, cloud layers, or dashboard noise.
 
+## Install
+
+### Homebrew
+
+```bash
+brew tap oliverjessner/tap
+brew install sqlite-hub
+```
+
+### NPM
+
+```bash
+npm install -g sqlite-hub
+```
+
+## Alternative port
+
+```bash
+sqlite-hub --port:4174
+```
+
 ## Why SQLite Hub?
 
 Many database tools are powerful, but feel oversized when all you want is to inspect a local SQLite file, edit a few rows, and run a query fast.
@@ -18,6 +39,7 @@ SQLite Hub keeps that workflow sharp:
 - inspect database health, storage metrics, and schema connectivity from one overview
 - filter, sort, page through, and export table data
 - inspect schema, structure, and relationships
+- generate TypeScript, Rust, Kotlin, or Swift types from table schemas
 - edit records in place with typed value previews and an SQL diff preview before saving
 - export tables and query results as CSV, TSV, Markdown, JSON, Parquet, or duplicate them as a table
 - copy result columns with formatting, headers, first-10 previews, TXT export, and Markdown todo export
@@ -32,45 +54,40 @@ SQLite Hub keeps that workflow sharp:
 
 ## Features
 
-### Connections
-
-[![SQLite Hub connections](./frontend/assets/mockups/connections_1200.webp)](./frontend/assets/mockups/connections_1200.webp)
-
-Open an existing SQLite file with a native file picker or create a new database with a native save dialog from the Connections view. Manual absolute-path entry remains available as a fallback for both actions.
-
-Recent connections show file size, modification time, last-opened time, and access mode. Connections can be activated, relabeled, moved to another path, opened read-only, assigned a PNG/JPG/WEBP icon, reset to the default icon, or removed from the recent-connections registry without deleting the database file.
+### Structure view
 
-### Overview
+[![SQLite Hub relationship graph](./frontend/assets/mockups/structure_1_1920.webp)](./frontend/assets/mockups/structure_1_1920.webp)
 
-The database overview combines operational and schema information for the active database:
+Inspect tables, views, indexes, triggers, columns, declared types, primary keys, nullability, foreign keys, and DDL without losing pace. The searchable object list and relationship graph support fit, relayout, selection clearing, direct navigation to table data, and a hideable inspector/sidebar. Clicking a relationship edge opens a join preview with the mapped columns and a copyable SQL `JOIN` snippet.
 
-- file size, page count, table/view counts, index/trigger counts, journal mode, and foreign-key status
-- largest tables by row count and estimated size
-- database path, modification time, SQLite version, page size, freelist count, and encoding
-- schema-map statistics for foreign-key links, connected clusters, and isolated tables
-- integrity and quick-check results, access mode, user version, and schema version
-- shortcuts to the SQL Editor, Structure view, and the database location in Finder
-
-### Structure view
+### Generate Types
 
 <p>
-  <a href="./frontend/assets/mockups/structure_1_1200.webp"><img src="./frontend/assets/mockups/structure_1_1200.webp" alt="SQLite Hub relationship graph" width="49%"></a>
-  <a href="./frontend/assets/mockups/structure_2_inspector_1200.webp"><img src="./frontend/assets/mockups/structure_2_inspector_1200.webp" alt="SQLite Hub structure inspector" width="49%"></a>
+  <a href="./frontend/assets/mockups/structure_2_generate_types_modal_1920.webp"><img src="./frontend/assets/mockups/structure_2_generate_types_modal_1920.webp" alt="SQLite Hub generate types for selected table" width="49%"></a>
+  <a href="./frontend/assets/mockups/structure_3_generate_types_modal_1920.webp"><img src="./frontend/assets/mockups/structure_3_generate_types_modal_1920.webp" alt="SQLite Hub generate types for all tables" width="49%"></a>
 </p>
 
-Inspect tables, views, indexes, triggers, columns, declared types, primary keys, nullability, foreign keys, and DDL without losing pace. The searchable object list and relationship graph support fit, relayout, selection clearing, direct navigation to table data, and a hideable inspector/sidebar. Clicking a relationship edge opens a join preview with the mapped columns and a copyable SQL `JOIN` snippet. SQLite Hub remembers the last selected table while you move between views, and DDL can be copied directly from the inspector.
+Generate application types directly from the Structure toolbar for the selected table or for every table in the database. The `Generate Types` dropdown lets you choose `Selected table` or `All tables`; the preview modal supports TypeScript, Rust, Kotlin, and Swift. When all tables are selected, SQLite Hub creates one generated file per table.
+
+Type generation uses SQLite's declared column types plus schema constraints such as primary keys, foreign keys, `NOT NULL`, generated columns, defaults, and simple `CHECK (... IN (...))` value sets.
+
+The same generator is available through the [CLI](./docs/CLI.md) and [local API](./docs/API.md) for automation.
 
 ### Data browser
 
-[![SQLite Hub data browser](./frontend/assets/mockups/data_1_1200.webp)](./frontend/assets/mockups/data_1_1200.webp)
+[![SQLite Hub data browser](./frontend/assets/mockups/data_1_1920.webp)](./frontend/assets/mockups/data_1_1920.webp)
 
-Scan rows, sort columns, move through local data quickly, and export full tables as CSV, TSV, Markdown, JSON, or Parquet. The Data browser also supports duplicating exports as a new table, searchable and hideable table navigation, page sizes up to 250 rows, and advanced filters with column/operator/value controls. Text filters support case-insensitive `contains`, `not contains`, and exact `equals` matching.
+Scan rows, sort columns, move through local data quickly, and export full tables as CSV, TSV, Markdown, JSON, or Parquet.
+
+The Data browser also supports duplicating exports as a new table, searchable and hideable table navigation, page sizes up to 250 rows, and advanced filters with column/operator/value controls. Text filters support case-insensitive `contains`, `not contains`, and exact `equals` matching.
 
 Wide tables keep their horizontal scroll position when sorting causes the grid to re-render. Cells use compact previews for long values, BLOBs, and detected file paths, while exports retain complete BLOB content.
 
+[![SQLite Hub data export modal](./frontend/assets/mockups/data_3_data_export_modal_1920.webp)](./frontend/assets/mockups/data_3_data_export_modal_1920.webp)
+
 ### Row editing
 
-[![SQLite Hub row editor](./frontend/assets/mockups/data_2_row_editor_1200.webp)](./frontend/assets/mockups/data_2_row_editor_1200.webp)
+[![SQLite Hub row editor](./frontend/assets/mockups/data_2_roweditor_1920.webp)](./frontend/assets/mockups/data_2_roweditor_1920.webp)
 
 Open one record, edit it in place, preview the generated SQL and changed values, then commit or delete the row with confirmation. SQLite Hub only enables row edits when it can target a stable primary-key or rowid identity safely.
 
@@ -87,40 +104,37 @@ The Row Editor adds contextual previews without changing the stored raw value:
 
 ### SQL editor
 
-[![SQLite Hub SQL editor](./frontend/assets/mockups/sql_editor_1_1200.webp)](./frontend/assets/mockups/sql_editor_1_1200.webp)
+[![SQLite Hub SQL editor](./frontend/assets/mockups/sql_editor_1_1920.webp)](./frontend/assets/mockups/sql_editor_1_1920.webp)
 
-Write queries in a syntax-highlighted editor, execute them with the Run button or `Shift + Enter`, format SQL with the editor Format button, inspect results in the same workflow, and export result sets as CSV, TSV, Markdown, JSON, Parquet, or duplicate them as a table. Query drafts survive reloads, query history can be searched and saved, and direct single-table `SELECT` results can be edited or deleted from the result grid when a stable row identity is available.
+Write queries in a syntax-highlighted editor, execute them with the Run button or `Shift + Enter`, format SQL with the editor Format button, inspect results in the same workflow, and export result sets as CSV, TSV, Markdown, JSON, Parquet, or duplicate them as a table.
 
-Interactive result sets are limited to the first 5,000 rows to keep the application responsive. A visible notice and Messages entry indicate truncation; CSV, TSV, Markdown, JSON, Parquet, and duplicate-table exports execute without that interactive row limit and include complete BLOB values. Sorting wide results preserves the horizontal scroll position.
+Query drafts survive reloads, query history can be searched and saved, and direct single-table `SELECT` results can be edited or deleted from the result grid when a stable row identity is available.
 
-[![SQLite Hub query export](./frontend/assets/mockups/sql_editor_5_export_query_result_1200.webp)](./frontend/assets/mockups/sql_editor_5_export_query_result_1200.webp)
+[![SQLite Hub query export](./frontend/assets/mockups/sql_editor_3_query_export_modal_1920.webp)](./frontend/assets/mockups/sql_editor_3_query_export_modal_1920.webp)
 
 Result column menus include copy actions for a full column, a column with header, or the first 10 values. The same modal can preview the output, copy it, export it as TXT, or turn a column into Markdown todo items.
 
-<p>
-  <a href="./frontend/assets/mockups/sql_editor_3_export_column_1200.webp"><img src="./frontend/assets/mockups/sql_editor_3_export_column_1200.webp" alt="SQLite Hub copy column dialog" width="49%"></a>
-  <a href="./frontend/assets/mockups/sql_editor_4_export_column_as_markdown_1200.webp"><img src="./frontend/assets/mockups/sql_editor_4_export_column_as_markdown_1200.webp" alt="SQLite Hub Markdown todo export" width="49%"></a>
-</p>
-
 The bottom panel keeps separate tabs for:
 
 - Results
 - Performance, including execution time, statement count, returned rows, affected rows, and serialized result memory size
 - Messages, including the executed query and statement updates/errors
 
-Potentially destructive statements are tracked in query history, and SQLite Hub keeps the active result tab instead of forcing you back to Results after every execution. Multi-statement SQL is reported statement by statement, including returned rows, affected rows, truncation warnings, executed SQL, errors, timing, and serialized result size.
+Potentially destructive statements are tracked in query history, and SQLite Hub keeps the active result tab instead of forcing you back to Results after every execution.
+
+Multi-statement SQL is reported statement by statement, including returned rows, affected rows, truncation warnings, executed SQL, errors, timing, and serialized result size.
 
 ### Query history
 
-[![SQLite Hub query history details](./frontend/assets/mockups/sql_editor_2_query_details_1200.webp)](./frontend/assets/mockups/sql_editor_2_query_details_1200.webp)
+[![SQLite Hub query history details](./frontend/assets/mockups/sql_editor_2_query_detail_1920.webp)](./frontend/assets/mockups/sql_editor_2_query_detail_1920.webp)
 
 SQLite Hub stores query history per database. You can browse recent and saved tabs, search SQL, titles, and notes, assign titles and notes, mark useful queries as saved, delete history entries, load older entries, re-run previous queries, reopen them in the editor, and execute saved queries from the CLI.
 
 ### Documents
 
-[![SQLite Hub Markdown documents](./frontend/assets/mockups/documents_1200.webp)](./frontend/assets/mockups/documents_1200.webp)
+[![SQLite Hub Markdown documents](./frontend/assets/mockups/documents_1_1920.webp)](./frontend/assets/mockups/documents_1_1920.webp)
 
-Documents are local Markdown notes scoped to the active database. SQLite Hub creates a document folder per database, keeps the sidebar fixed while the editor and preview panes scroll independently, and autosaves changes after a short debounce. You can create, rename, delete, import `.md` files, export the current document as Markdown, and toggle the editor or preview pane as needed.
+Documents are local Markdown notes scoped to the active database. SQLite Hub creates a document folder per database. You can import `.md` files, export the current document as Markdown.
 
 The preview supports regular Markdown, ordered and unordered lists, tables, code blocks, links, and clickable task-list checkboxes. Documents can also pull context from saved SQL Editor queries:
 
@@ -128,56 +142,64 @@ The preview supports regular Markdown, ordered and unordered lists, tables, code
 - Insert Note opens saved queries that have notes and inserts the selected note directly into the document.
 - Markdown Todo column exports from query results can create a new document without embedding the original SQL query.
 
+<p>
+  <a href="./frontend/assets/mockups/documents_2_document_insert_table_modal_1920.webp"><img src="./frontend/assets/mockups/documents_2_document_insert_table_modal_1920.webp" alt="SQLite Hub insert saved query table into a document" width="49%"></a>
+  <a href="./frontend/assets/mockups/documents_3_document_insert_note_modal_1920.webp"><img src="./frontend/assets/mockups/documents_3_document_insert_note_modal_1920.webp" alt="SQLite Hub insert saved query note into a document" width="49%"></a>
+</p>
+
 ### Charts
 
-[![SQLite Hub bar chart](./frontend/assets/mockups/charts_1_bars_1200.webp)](./frontend/assets/mockups/charts_1_bars_1200.webp)
+[![SQLite Hub charts](./frontend/assets/mockups/charts_1_1920.webp)](./frontend/assets/mockups/charts_1_1920.webp)
 
 Create bar, line, pie/donut, and scatter charts from chartable `SELECT` query-history entries. Charts can be saved per query, edited, deleted, resized, reopened later, rendered from live query results, and exported as PNG. Chart configuration supports compatible column selection, sorting, labels, legends, line smoothing, scatter series, and optional scatter point sizing.
 
 <p>
-  <a href="./frontend/assets/mockups/charts_2_pie_1200.webp"><img src="./frontend/assets/mockups/charts_2_pie_1200.webp" alt="SQLite Hub pie chart" width="49%"></a>
-  <a href="./frontend/assets/mockups/charts_3_scatter_plot_1200.webp"><img src="./frontend/assets/mockups/charts_3_scatter_plot_1200.webp" alt="SQLite Hub scatter plot" width="49%"></a>
+  <a href="./frontend/assets/mockups/charts_2_query_detail_1920.webp"><img src="./frontend/assets/mockups/charts_2_query_detail_1920.webp" alt="SQLite Hub chart query detail drawer" width="49%"></a>
+  <a href="./frontend/assets/mockups/charts_3_create_query_chart_modal_1920.webp"><img src="./frontend/assets/mockups/charts_3_create_query_chart_modal_1920.webp" alt="SQLite Hub create chart modal" width="49%"></a>
+</p>
+
+<p>
+  <a href="./frontend/assets/mockups/charts_4_edit_query_chart_modal_1920.webp"><img src="./frontend/assets/mockups/charts_4_edit_query_chart_modal_1920.webp" alt="SQLite Hub edit chart modal" width="49%"></a>
+  <a href="./frontend/assets/mockups/charts_5_delete_query_chart_modal_1920.webp"><img src="./frontend/assets/mockups/charts_5_delete_query_chart_modal_1920.webp" alt="SQLite Hub delete chart modal" width="49%"></a>
 </p>
 
+[![SQLite Hub chart column copy modal](./frontend/assets/mockups/charts_6_copy_column_modal_1920.webp)](./frontend/assets/mockups/charts_6_copy_column_modal_1920.webp)
+
 ### Table Designer
 
-[![SQLite Hub Table Designer](./frontend/assets/mockups/table_designer_1_1200.webp)](./frontend/assets/mockups/table_designer_1_1200.webp)
+[![SQLite Hub Table Designer](./frontend/assets/mockups/table_designer_1_1920.webp)](./frontend/assets/mockups/table_designer_1_1920.webp)
 
 Create and edit SQLite tables from the UI. The Table Designer includes a searchable table list, validation and migration warnings, and controls for column names, SQLite types, `NOT NULL`, `UNIQUE`, primary keys, SQL defaults, foreign-key tables/columns, and check constraints. Existing composite unique constraints are surfaced as schema metadata.
 
 CSV files can seed a new table draft and optionally fill the created table with imported rows. Every change produces a copyable live SQL preview that can be hidden or shown before the schema operation is applied.
 
-[![SQLite Hub Table Designer checks](./frontend/assets/mockups/table_designer_2_checks_1200.webp)](./frontend/assets/mockups/table_designer_2_checks_1200.webp)
+[![SQLite Hub Table Designer constraints](./frontend/assets/mockups/table_designer_2_table_designer_constraints_modal_1920.webp)](./frontend/assets/mockups/table_designer_2_table_designer_constraints_modal_1920.webp)
 
 ### Media Tagging
 
-[![SQLite Hub Media Tagging setup](./frontend/assets/mockups/media_tagging_1_setup_1200.webp)](./frontend/assets/mockups/media_tagging_1_setup_1200.webp)
+[![SQLite Hub Media Tagging setup](./frontend/assets/mockups/media_tagging_setup_1_1920.webp)](./frontend/assets/mockups/media_tagging_setup_1_1920.webp)
 
 Configure a media table, path/status columns, tag table, mapping table, and the SQL queries that drive tagged and untagged queues. SQLite Hub can create the default tag and mapping tables, validate the setup, reset default queries, and preview image, video, and audio assets from paths scoped to the active database directory.
 
-The queue supports tag search, tag creation/removal, parent tags, copying tags from the previous item, applying selected tags, skipping items, resetting skipped items, rotating visual media, hiding/showing media details, and opening the current row in Data or Structure. `Shift + Enter` applies the selected tags and advances to the next item.
-
 <p>
-  <a href="./frontend/assets/mockups/media_tagging_2_tagging_queue_1200.webp"><img src="./frontend/assets/mockups/media_tagging_2_tagging_queue_1200.webp" alt="SQLite Hub tagging queue" width="49%"></a>
-  <a href="./frontend/assets/mockups/media_tagging_3_media_viewer_1200.webp"><img src="./frontend/assets/mockups/media_tagging_3_media_viewer_1200.webp" alt="SQLite Hub media viewer" width="49%"></a>
+  <a href="./frontend/assets/mockups/media_tagging_setup_2_create_media_tagging_tag_table_modal_1920.webp"><img src="./frontend/assets/mockups/media_tagging_setup_2_create_media_tagging_tag_table_modal_1920.webp" alt="SQLite Hub create media tagging tag table modal" width="49%"></a>
+  <a href="./frontend/assets/mockups/media_tagging_setup_3_create_media_tagging_mapping_table_modal_1920.webp"><img src="./frontend/assets/mockups/media_tagging_setup_3_create_media_tagging_mapping_table_modal_1920.webp" alt="SQLite Hub create media tagging mapping table modal" width="49%"></a>
 </p>
 
-### UI preferences
+The queue supports tag search, tag creation/removal, parent tags, copying tags from the previous item, applying selected tags, skipping items, resetting skipped items, rotating visual media, hiding/showing media details, and opening the current row in Data or Structure. `Shift + Enter` applies the selected tags and advances to the next item.
 
-SQLite Hub remembers common workspace preferences in local storage, including hidden panels, selected editor tabs, query drafts, chart panels, table row size, and Table Designer preview visibility.
+[![SQLite Hub tagging queue](./frontend/assets/mockups/media_tagging_queue_1_1920.webp)](./frontend/assets/mockups/media_tagging_queue_1_1920.webp)
 
 ### Settings
 
-[![SQLite Hub settings](./frontend/assets/mockups/settings_1200.webp)](./frontend/assets/mockups/settings_1200.webp)
-
-The Settings view reports the installed SQLite Hub version and the actual SQLite runtime version used to execute queries. It also keeps the custom-port CLI command, project website, and source repository available in the application.
+[![SQLite Hub settings](./frontend/assets/mockups/settings_1_1920.webp)](./frontend/assets/mockups/settings_1_1920.webp)
 
-### Database quick picks
-
-The active database footer in the sidebar opens a quick-pick panel with the five most recent databases, so you can switch databases without going back to the Connections view.
+The Settings view reports the installed SQLite Hub version and the actual SQLite runtime version used to execute queries.
 
 ### Backup Manager
 
+[![SQLite Hub backups](./frontend/assets/mockups/backups_1_1920.webp)](./frontend/assets/mockups/backups_1_1920.webp)
+
 Create verified local backups of the active SQLite database, review backup metadata, edit backup notes, download backup files, restore verified backups, and delete managed backups from the Backups view. SQLite Hub stores backup files under its local app-state backup directory by connection id and keeps a `manifest.json` beside each database's backup files. Each backup is created through SQLite's backup API, hashed with SHA-256, and verified with `PRAGMA quick_check` before it is marked as verified.
 
 SQLite Hub also proposes a safety backup before operations that can be hard to undo:
@@ -189,41 +211,52 @@ SQLite Hub also proposes a safety backup before operations that can be hard to u
 
 The safety dialog lets you create the backup and continue, continue without creating one, or cancel the operation.
 
-### Local-first
+<p>
+  <a href="./frontend/assets/mockups/backups_2_create_backup_modal_1920.webp"><img src="./frontend/assets/mockups/backups_2_create_backup_modal_1920.webp" alt="SQLite Hub create backup modal" width="49%"></a>
+  <a href="./frontend/assets/mockups/backups_3_edit_backup_modal_1920.webp"><img src="./frontend/assets/mockups/backups_3_edit_backup_modal_1920.webp" alt="SQLite Hub edit backup modal" width="49%"></a>
+</p>
 
-Built around local SQLite files, not hosted dashboards or team complexity. The server binds explicitly to the IPv4 loopback interface, and API middleware rejects foreign hosts and cross-origin mutations while still allowing same-origin browser and local CLI requests.
+<p>
+  <a href="./frontend/assets/mockups/backups_4_restore_backup_modal_1920.webp"><img src="./frontend/assets/mockups/backups_4_restore_backup_modal_1920.webp" alt="SQLite Hub restore backup modal" width="49%"></a>
+  <a href="./frontend/assets/mockups/backups_5_delete_backup_modal_1920.webp"><img src="./frontend/assets/mockups/backups_5_delete_backup_modal_1920.webp" alt="SQLite Hub delete backup modal" width="49%"></a>
+</p>
 
-## Install
+### Overview
 
-### Homebrew
+The database overview combines operational and schema information for the active database:
 
-```bash
-brew tap oliverjessner/tap
-brew install sqlite-hub
-```
+- file size, page count, table/view counts, index/trigger counts, journal mode, and foreign-key status
+- largest tables by row count and estimated size
+- database path, modification time, SQLite version, page size, freelist count, and encoding
+- schema-map statistics for foreign-key links, connected clusters, and isolated tables
+- integrity and quick-check results, access mode, user version, and schema version
+- shortcuts to the SQL Editor, Structure view, and the database location in Finder
 
-### NPM
+### Connections
 
-```bash
-npm install -g sqlite-hub
-```
+[![SQLite Hub connections](./frontend/assets/mockups/connections_1_1920.webp)](./frontend/assets/mockups/connections_1_1920.webp)
 
-## Alternative port
+Recent connections show file size, modification time, last-opened time, and access mode. Connections can be activated, relabeled, moved to another path, opened read-only, assigned a PNG/JPG/WEBP icon, reset to the default icon, or removed from the recent-connections registry without deleting the database file.
 
-```bash
-sqlite-hub --port:4174
-```
+<p>
+  <a href="./frontend/assets/mockups/connections_2_create_connection_modal_1920.webp"><img src="./frontend/assets/mockups/connections_2_create_connection_modal_1920.webp" alt="SQLite Hub create connection modal" width="49%"></a>
+  <a href="./frontend/assets/mockups/connections_3_open_connection_modal_1920.webp"><img src="./frontend/assets/mockups/connections_3_open_connection_modal_1920.webp" alt="SQLite Hub open connection modal" width="49%"></a>
+</p>
+
+### Local-first
+
+Built around local SQLite files, not hosted dashboards or team complexity. The server binds explicitly to the IPv4 loopback interface, and API middleware rejects foreign hosts and cross-origin mutations while still allowing same-origin browser and local CLI requests.
 
 ## CLI
 
 SQLite Hub ships with a built-in CLI for starting the app, inspecting imported
 databases, executing raw or saved SQL, exporting query results, exporting single
-rows as JSON, and working with Markdown documents. See the
+rows as JSON, generating schema types, and working with Markdown documents. See the
 [CLI documentation](./docs/CLI.md) for commands, flags, and examples.
 
 ## API
 
-SQLite Hub also provides a local JSON API for app info, database metadata, tables, saved queries, exports, and documents. `/api/v1/info` returns the same app/version status as `sqlite-hub --info`; database data is protected by database-specific API tokens created in Settings. See the [API documentation](./docs/API.md) for authentication, endpoints, and examples.
+SQLite Hub also provides a local JSON API for app info, database metadata, tables, saved queries, exports, documents, and schema type generation. `/api/v1/info` returns the same app/version status as `sqlite-hub --info`; database data is protected by database-specific API itokens created in Settings. See the [API documentation](./docs/API.md) for authentication, endpoints, and examples.
 
 ## Changelog
 

package/bin/sqlite-hub.js

@@ -5,6 +5,7 @@ const path = require('node:path');
 const { spawn } = require('node:child_process');
 const { DatabaseCommandService, getQueryTitle } = require('../server/services/databaseCommandService');
 const { buildAppInfo } = require('../server/services/appInfoService');
+const { FILE_EXTENSIONS } = require('../server/services/typeGenerationService');
 
 const DEFAULT_PORT = 4173;
 const EXPORT_FORMATS = new Set(['csv', 'tsv', 'md', 'json']);
@@ -27,6 +28,7 @@ Usage:
   sqlite-hub --database:"name" --documents:"Document Name" --export
   sqlite-hub --database:"name" --table:"table_name"
   sqlite-hub --database:"name" --table:"table_name" --export:"primary-key"
+  sqlite-hub --database:"name" --table:"table_name" --types:typescript
 
 Options:
   --help, -h                         Show this help text.
@@ -53,6 +55,21 @@ Options:
   --documents:"name" --export        Export a document as a Markdown file.
   --table:"table"                    Print table metadata.
   --table:"table" --export:"pk"      Export one row as JSON by primary key or rowid.
+  --types:typescript|ts|rust|rs|kotlin|kt|swift
+                                      Generate application types for --table.
+  --type-name:"name"                 Override generated type name.
+  --naming:preserve|camel|pascal|snake
+                                      Select generated property naming.
+  --nullable:native|optional          Select nullable handling. Optional is TypeScript only.
+  --comments                         Include schema comments.
+  --defaults-as-comments             Include default values in comments.
+  --json-type:unknown|record|json-value
+                                      Select TypeScript JSON mapping.
+  --include-generated                Include generated columns.
+  --include-hidden                   Include hidden columns.
+  --output:"file"                    Write generated types to a file.
+  --json                             Print generated type result as JSON.
+  --force                            Overwrite --output file if it exists.
 `);
 }
 
@@ -175,6 +192,18 @@ function parseCliArguments(argv) {
         documentName: null,
         documentExport: false,
         tableName: null,
+        typesTarget: null,
+        typeName: null,
+        naming: null,
+        nullableMode: null,
+        includeComments: false,
+        includeDefaultsAsComments: false,
+        includeGeneratedColumns: undefined,
+        includeHiddenColumns: false,
+        jsonType: null,
+        outputPath: null,
+        jsonOutput: false,
+        force: false,
     };
 
     for (let index = 0; index < argv.length; index += 1) {
@@ -384,6 +413,78 @@ function parseCliArguments(argv) {
             continue;
         }
 
+        if (flag === '--types') {
+            const parsed = takeFlagValue(flag, value, argv, index);
+            options.typesTarget = parsed.value;
+            index = parsed.nextIndex;
+            continue;
+        }
+
+        if (flag === '--type-name') {
+            const parsed = takeFlagValue(flag, value, argv, index);
+            options.typeName = parsed.value;
+            index = parsed.nextIndex;
+            continue;
+        }
+
+        if (flag === '--naming') {
+            const parsed = takeFlagValue(flag, value, argv, index);
+            options.naming = parsed.value;
+            index = parsed.nextIndex;
+            continue;
+        }
+
+        if (flag === '--nullable') {
+            const parsed = takeFlagValue(flag, value, argv, index);
+            options.nullableMode = parsed.value;
+            index = parsed.nextIndex;
+            continue;
+        }
+
+        if (flag === '--comments') {
+            options.includeComments = true;
+            continue;
+        }
+
+        if (flag === '--defaults-as-comments') {
+            options.includeDefaultsAsComments = true;
+            continue;
+        }
+
+        if (flag === '--include-generated') {
+            options.includeGeneratedColumns = true;
+            continue;
+        }
+
+        if (flag === '--include-hidden') {
+            options.includeHiddenColumns = true;
+            continue;
+        }
+
+        if (flag === '--json-type') {
+            const parsed = takeFlagValue(flag, value, argv, index);
+            options.jsonType = parsed.value;
+            index = parsed.nextIndex;
+            continue;
+        }
+
+        if (flag === '--output') {
+            const parsed = takeFlagValue(flag, value, argv, index);
+            options.outputPath = parsed.value;
+            index = parsed.nextIndex;
+            continue;
+        }
+
+        if (flag === '--json') {
+            options.jsonOutput = true;
+            continue;
+        }
+
+        if (flag === '--force') {
+            options.force = true;
+            continue;
+        }
+
         throw new Error(`Unknown argument: ${argument}`);
     }
 
@@ -406,7 +507,8 @@ function hasDatabaseOperation(options) {
         options.documentName ||
         options.documentExport ||
         options.exportTarget ||
-        options.tableName,
+        options.tableName ||
+        options.typesTarget,
     );
 }
 
@@ -626,6 +728,67 @@ function exportSavedQuery({ databaseService, conn, queryName, format }) {
     console.log(`File: ${outputPath}`);
 }
 
+function buildTypeOptions(options) {
+    const typeOptions = {};
+
+    if (options.typeName) typeOptions.typeName = options.typeName;
+    if (options.naming) typeOptions.propertyNaming = options.naming;
+    if (options.nullableMode) typeOptions.nullableMode = options.nullableMode;
+    if (options.includeComments) typeOptions.includeComments = true;
+    if (options.includeDefaultsAsComments) typeOptions.includeDefaultsAsComments = true;
+    if (options.includeGeneratedColumns !== undefined) {
+        typeOptions.includeGeneratedColumns = options.includeGeneratedColumns;
+    }
+    if (options.includeHiddenColumns) typeOptions.includeHiddenColumns = true;
+    if (options.jsonType) typeOptions.jsonType = options.jsonType;
+
+    return typeOptions;
+}
+
+function generateTypes({ databaseService, conn, tableName, options }) {
+    if (!tableName) {
+        throw new Error('--types requires --database and --table.');
+    }
+
+    if (options.jsonOutput && options.outputPath) {
+        throw new Error('--json cannot be combined with --output.');
+    }
+
+    const result = databaseService.generateTableTypes(
+        conn.id,
+        tableName,
+        options.typesTarget,
+        buildTypeOptions(options)
+    );
+
+    if (options.jsonOutput) {
+        console.log(JSON.stringify(result, null, 2));
+        return;
+    }
+
+    if (options.outputPath) {
+        const outputPath = path.resolve(process.cwd(), options.outputPath);
+        const expectedExtension = FILE_EXTENSIONS[result.target];
+
+        if (path.extname(outputPath) !== expectedExtension) {
+            throw new Error(`Output file for ${result.target} must use ${expectedExtension}.`);
+        }
+
+        if (!options.force && fs.existsSync(outputPath)) {
+            throw new Error(`Output file already exists: ${outputPath}`);
+        }
+
+        fs.mkdirSync(path.dirname(outputPath), { recursive: true });
+        fs.writeFileSync(outputPath, result.code, 'utf8');
+        result.warnings.forEach(warning => console.error(`Warning: ${warning}`));
+        console.error(`Generated ${result.target} types: ${outputPath}`);
+        return;
+    }
+
+    result.warnings.forEach(warning => console.error(`Warning: ${warning}`));
+    process.stdout.write(`${result.code}\n`);
+}
+
 function listDocuments(databaseService, conn) {
     const documents = databaseService.listDocuments(conn.id);
 
@@ -877,9 +1040,20 @@ async function main(argv = process.argv.slice(2), dependencies = {}) {
             options.rawQuery ||
             options.showQuery ||
             options.showNotes ||
-            options.exportTarget
+            options.exportTarget ||
+            options.typesTarget
         ) {
             if (options.tableName) {
+                if (options.typesTarget) {
+                    generateTypes({
+                        databaseService,
+                        conn,
+                        tableName: options.tableName,
+                        options,
+                    });
+                    return;
+                }
+
                 if (options.exportTarget) {
                     exportTableRowAsJson({
                         databaseService,