@carllee1983/dbcli 1.4.0 → 1.4.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +18 -0
- package/assets/SKILL.md +8 -2
- package/dist/cli.mjs +1 -1
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,24 @@ All notable changes to dbcli are documented here.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
+
## [1.4.1] - 2026-04-21
|
|
9
|
+
|
|
10
|
+
### Added
|
|
11
|
+
|
|
12
|
+
- **Documentation Update**: Added per-connection schema isolation details to `SKILL.md` for AI agents.
|
|
13
|
+
- Clarified schema storage layout in `.dbcli/schemas/`.
|
|
14
|
+
- Added usage examples for `--use <connection>` with schema commands.
|
|
15
|
+
|
|
16
|
+
## [1.4.0] - 2026-04-21
|
|
17
|
+
|
|
18
|
+
### Added
|
|
19
|
+
|
|
20
|
+
- **Layered Schema Cache (Wave 1)**: Integrated file-based persistence for database schemas.
|
|
21
|
+
- New `SchemaWriter` for saving schema snapshots to `.dbcli/schemas/`.
|
|
22
|
+
- Layered schema loading (Hot/Cold) integrated into `configModule`.
|
|
23
|
+
- Per-connection isolation: Each connection now has its own schema directory (`.dbcli/schemas/<connection>/`).
|
|
24
|
+
- **Improved Migration UX**: Added proactive hints during schema migration to ensure data consistency.
|
|
25
|
+
|
|
8
26
|
## [1.3.0] - 2026-04-02
|
|
9
27
|
|
|
10
28
|
### Added
|
package/assets/SKILL.md
CHANGED
|
@@ -75,17 +75,23 @@ dbcli list --format json
|
|
|
75
75
|
Display table schema or scan entire database.
|
|
76
76
|
|
|
77
77
|
```bash
|
|
78
|
-
dbcli schema # Scan all tables, save to .dbcli
|
|
78
|
+
dbcli schema # Scan all tables, save to .dbcli/schemas/
|
|
79
79
|
dbcli schema users # Show single table schema
|
|
80
80
|
dbcli schema users --format json
|
|
81
81
|
dbcli schema --refresh # Detect and apply schema changes
|
|
82
82
|
dbcli schema --reset # Clear all schema data and re-fetch
|
|
83
83
|
dbcli schema --reset --force # Skip confirmation
|
|
84
|
+
|
|
85
|
+
# Per-connection schema isolation (v2 multi-connection config)
|
|
86
|
+
dbcli schema --use staging # Scan staging DB; saves to .dbcli/schemas/staging/
|
|
87
|
+
dbcli schema --use prod # Scan prod DB; saves to .dbcli/schemas/prod/
|
|
84
88
|
```
|
|
85
89
|
|
|
86
|
-
**Options:** `--format <table|json>`, `--refresh`, `--reset`, `--force
|
|
90
|
+
**Options:** `--format <table|json>`, `--refresh`, `--reset`, `--force`, `--use <connection>`
|
|
87
91
|
**Permission:** query-only+
|
|
88
92
|
|
|
93
|
+
**Schema storage (v1.4+):** Schema is persisted as layered files under `.dbcli/schemas/`. With v2 multi-connection config each connection gets its own subdirectory (`.dbcli/schemas/<connection>/`). Run `dbcli schema --use <connection>` once per connection before querying it — otherwise `schema <table>` may return data from the wrong connection's cache.
|
|
94
|
+
|
|
89
95
|
### query
|
|
90
96
|
|
|
91
97
|
Execute SQL query.
|
package/dist/cli.mjs
CHANGED
|
@@ -48307,7 +48307,7 @@ var {
|
|
|
48307
48307
|
// package.json
|
|
48308
48308
|
var package_default = {
|
|
48309
48309
|
name: "@carllee1983/dbcli",
|
|
48310
|
-
version: "1.4.
|
|
48310
|
+
version: "1.4.1",
|
|
48311
48311
|
description: "Database CLI for AI agents",
|
|
48312
48312
|
type: "module",
|
|
48313
48313
|
publishConfig: {
|