dirsql 0.3.72__tar.gz → 0.3.73__tar.gz

{dirsql-0.3.72 → dirsql-0.3.73}/Cargo.lock

@@ -500,7 +500,7 @@ dependencies = [
 
 [[package]]
 name = "dirsql-py-ext"
-version = "0.3.72"
+version = "0.3.73"
 dependencies = [
  "dirsql",
  "pyo3",

{dirsql-0.3.72 → dirsql-0.3.73}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dirsql
-Version: 0.3.72
+Version: 0.3.73
 Summary: Ephemeral SQL index over a local directory
 Keywords: sql,filesystem,directory,sqlite,index
 Author: Kevin Scott

{dirsql-0.3.72/packages/rust → dirsql-0.3.73}/docs/howto/columns-from-paths.md

@@ -29,12 +29,8 @@ within one path segment) are in
 
 ## 2. Query the captured columns
 
-Start the server (`npx dirsql` / `uvx dirsql`) and query:
-
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT year, month, _basename FROM photos ORDER BY year, month"}'
+dirsql query "SELECT year, month, _basename FROM photos ORDER BY year, month"
 ```
 
 ```json
@@ -44,9 +40,7 @@ curl -s http://localhost:7117/query \
 Captures are real SQL columns, so aggregation works:
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT year, COUNT(*) AS photos FROM photos GROUP BY year"}'
+dirsql query "SELECT year, COUNT(*) AS photos FROM photos GROUP BY year"
 ```
 
 ```json

{dirsql-0.3.72/packages/python → dirsql-0.3.73}/docs/howto/define-tables.md

@@ -24,26 +24,12 @@ glob = "posts/**/*.md"
   filesystem facts `dirsql` computes for every file. Facts are opt-in by
   DDL: only the ones you declare become columns.
 
-## 2. Start the server and query
-
-::: code-group
-
-```bash [npm]
-npx dirsql
-```
-
-```bash [PyPI]
-uvx dirsql
-```
-
-:::
+## 2. Query the table
 
 Each matched file is one row:
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT _path, _size FROM posts ORDER BY _path"}'
+dirsql query "SELECT _path, _size FROM posts ORDER BY _path"
 ```
 
 ```json

{dirsql-0.3.72/packages/python → dirsql-0.3.73}/docs/howto/extract-from-contents.md

@@ -31,12 +31,8 @@ by every hook.
 
 ## 2. Query the extracted columns
 
-Start the server (`npx dirsql` / `uvx dirsql`) and query:
-
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT title, author, year, _path FROM books ORDER BY year"}'
+dirsql query "SELECT title, author, year, _path FROM books ORDER BY year"
 ```
 
 ```json
@@ -61,9 +57,7 @@ on-file = "jq -c -s '.' {path}"
 ```
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT event, user FROM events"}'
+dirsql query "SELECT event, user FROM events"
 ```
 
 ```json

{dirsql-0.3.72/packages/python → dirsql-0.3.73}/docs/howto/load-extension.md

@@ -23,13 +23,10 @@ overrides the init symbol when it doesn't match the filename-derived
 default — `sqlite-vec` is exactly such a case
 ([reference](../reference/config.md#dirsql-extension)).
 
-Start the server (`npx dirsql` / `uvx dirsql`) and the extension's
-functions are callable:
+The extension's functions are callable:
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT vec_version() AS vec_version"}'
+dirsql query "SELECT vec_version() AS vec_version"
 ```
 
 ```json

{dirsql-0.3.72/packages/python → dirsql-0.3.73}/docs/howto/search-by-meaning.md

@@ -99,20 +99,14 @@ installed `sqlite_vec` module to its bundled loadable. Naming rules per
 runtime — and the literal-path alternative that works everywhere — are in
 [Load a SQLite extension](./load-extension.md).
 
-## 3. Start the server and ask questions
+## 3. Ask questions
 
-Launch with `sqlite-vec` available to the launcher's environment:
+Run with `sqlite-vec` available to the launcher's environment. The initial
+scan runs `embed.py` once per note, then the query argument goes straight to
+`pre-query`, exactly as a `POST /query` body would:
 
 ```bash
-uvx --with sqlite-vec dirsql
-```
-
-The initial scan runs `embed.py` once per note. Then ask:
-
-```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"q": "how do I cook pasta?"}'
+uvx --with sqlite-vec dirsql query '{"q": "how do I cook pasta?"}'
 ```
 
 ```json
@@ -120,9 +114,7 @@ curl -s http://localhost:7117/query \
 ```
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"q": "reviewing code on github"}'
+uvx --with sqlite-vec dirsql query '{"q": "reviewing code on github"}'
 ```
 
 ```json
@@ -133,9 +125,9 @@ Neither question shares a keyword with its top note — "cook" appears
 nowhere in `pasta.md`, "github" nowhere in `branches.md`. The distance
 ranking is doing the work.
 
-Because `pre-query` is set, the request body is *not* the usual
-`{"sql": …}` — the raw body goes to your script, which decides what SQL
-runs ([hook interactions](../reference/http-api.md#hook-interactions)).
+Because `pre-query` is set, the query argument is *not* the usual
+`{"sql": …}` — it goes to your script as-is, which decides what SQL runs
+([hook interactions](../reference/http-api.md#hook-interactions)).
 
 ## Recomputing vs. caching
 

{dirsql-0.3.72/packages/rust → dirsql-0.3.73}/docs/howto/skip-files.md

@@ -31,12 +31,8 @@ ignored file never reaches any table — even one whose glob would match it.
 
 ## 2. Confirm what made it in
 
-Start the server (`npx dirsql` / `uvx dirsql`) and check:
-
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT _path FROM notes ORDER BY _path"}'
+dirsql query "SELECT _path FROM notes ORDER BY _path"
 ```
 
 ```json

{dirsql-0.3.72 → dirsql-0.3.73}/packages/python/Cargo.toml

@@ -4,7 +4,7 @@ name = "dirsql-py-ext"
 # pypi/maturin handler can rewrite it via `write-version` before
 # `maturin build`. `pyproject.toml` declares `dynamic = ["version"]`
 # and maturin reads this field. Mirrors `packages/rust/Cargo.toml`.
-version = "0.3.72"
+version = "0.3.73"
 edition.workspace = true
 publish = false
 readme = "README.md"

{dirsql-0.3.72 → dirsql-0.3.73}/packages/python/docs/howto/columns-from-paths.md

@@ -29,12 +29,8 @@ within one path segment) are in
 
 ## 2. Query the captured columns
 
-Start the server (`npx dirsql` / `uvx dirsql`) and query:
-
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT year, month, _basename FROM photos ORDER BY year, month"}'
+dirsql query "SELECT year, month, _basename FROM photos ORDER BY year, month"
 ```
 
 ```json
@@ -44,9 +40,7 @@ curl -s http://localhost:7117/query \
 Captures are real SQL columns, so aggregation works:
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT year, COUNT(*) AS photos FROM photos GROUP BY year"}'
+dirsql query "SELECT year, COUNT(*) AS photos FROM photos GROUP BY year"
 ```
 
 ```json

{dirsql-0.3.72/packages/rust → dirsql-0.3.73/packages/python}/docs/howto/define-tables.md

@@ -24,26 +24,12 @@ glob = "posts/**/*.md"
   filesystem facts `dirsql` computes for every file. Facts are opt-in by
   DDL: only the ones you declare become columns.
 
-## 2. Start the server and query
-
-::: code-group
-
-```bash [npm]
-npx dirsql
-```
-
-```bash [PyPI]
-uvx dirsql
-```
-
-:::
+## 2. Query the table
 
 Each matched file is one row:
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT _path, _size FROM posts ORDER BY _path"}'
+dirsql query "SELECT _path, _size FROM posts ORDER BY _path"
 ```
 
 ```json

{dirsql-0.3.72/packages/rust → dirsql-0.3.73/packages/python}/docs/howto/extract-from-contents.md

@@ -31,12 +31,8 @@ by every hook.
 
 ## 2. Query the extracted columns
 
-Start the server (`npx dirsql` / `uvx dirsql`) and query:
-
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT title, author, year, _path FROM books ORDER BY year"}'
+dirsql query "SELECT title, author, year, _path FROM books ORDER BY year"
 ```
 
 ```json
@@ -61,9 +57,7 @@ on-file = "jq -c -s '.' {path}"
 ```
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT event, user FROM events"}'
+dirsql query "SELECT event, user FROM events"
 ```
 
 ```json

{dirsql-0.3.72/packages/rust → dirsql-0.3.73/packages/python}/docs/howto/load-extension.md

@@ -23,13 +23,10 @@ overrides the init symbol when it doesn't match the filename-derived
 default — `sqlite-vec` is exactly such a case
 ([reference](../reference/config.md#dirsql-extension)).
 
-Start the server (`npx dirsql` / `uvx dirsql`) and the extension's
-functions are callable:
+The extension's functions are callable:
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT vec_version() AS vec_version"}'
+dirsql query "SELECT vec_version() AS vec_version"
 ```
 
 ```json

{dirsql-0.3.72/packages/rust → dirsql-0.3.73/packages/python}/docs/howto/search-by-meaning.md

@@ -99,20 +99,14 @@ installed `sqlite_vec` module to its bundled loadable. Naming rules per
 runtime — and the literal-path alternative that works everywhere — are in
 [Load a SQLite extension](./load-extension.md).
 
-## 3. Start the server and ask questions
+## 3. Ask questions
 
-Launch with `sqlite-vec` available to the launcher's environment:
+Run with `sqlite-vec` available to the launcher's environment. The initial
+scan runs `embed.py` once per note, then the query argument goes straight to
+`pre-query`, exactly as a `POST /query` body would:
 
 ```bash
-uvx --with sqlite-vec dirsql
-```
-
-The initial scan runs `embed.py` once per note. Then ask:
-
-```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"q": "how do I cook pasta?"}'
+uvx --with sqlite-vec dirsql query '{"q": "how do I cook pasta?"}'
 ```
 
 ```json
@@ -120,9 +114,7 @@ curl -s http://localhost:7117/query \
 ```
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"q": "reviewing code on github"}'
+uvx --with sqlite-vec dirsql query '{"q": "reviewing code on github"}'
 ```
 
 ```json
@@ -133,9 +125,9 @@ Neither question shares a keyword with its top note — "cook" appears
 nowhere in `pasta.md`, "github" nowhere in `branches.md`. The distance
 ranking is doing the work.
 
-Because `pre-query` is set, the request body is *not* the usual
-`{"sql": …}` — the raw body goes to your script, which decides what SQL
-runs ([hook interactions](../reference/http-api.md#hook-interactions)).
+Because `pre-query` is set, the query argument is *not* the usual
+`{"sql": …}` — it goes to your script as-is, which decides what SQL runs
+([hook interactions](../reference/http-api.md#hook-interactions)).
 
 ## Recomputing vs. caching
 

{dirsql-0.3.72 → dirsql-0.3.73/packages/python}/docs/howto/skip-files.md

@@ -31,12 +31,8 @@ ignored file never reaches any table — even one whose glob would match it.
 
 ## 2. Confirm what made it in
 
-Start the server (`npx dirsql` / `uvx dirsql`) and check:
-
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT _path FROM notes ORDER BY _path"}'
+dirsql query "SELECT _path FROM notes ORDER BY _path"
 ```
 
 ```json

{dirsql-0.3.72 → dirsql-0.3.73}/packages/python/e2e-attestation.json

@@ -1,6 +1,6 @@
 {
   "command": "uv run python -m pytest tests/e2e/ -x -q",
-  "ran_at": 1783420501,
+  "ran_at": 1783427443,
   "exit_code": 0,
-  "commit": "fe9d09208be0b3c6084d9b916a41403d5822d096"
+  "commit": "16fc390f62d2f4f9d607eb28fc2adc8ee1d6ea0a"
 }

{dirsql-0.3.72 → dirsql-0.3.73/packages/rust}/docs/howto/columns-from-paths.md

@@ -29,12 +29,8 @@ within one path segment) are in
 
 ## 2. Query the captured columns
 
-Start the server (`npx dirsql` / `uvx dirsql`) and query:
-
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT year, month, _basename FROM photos ORDER BY year, month"}'
+dirsql query "SELECT year, month, _basename FROM photos ORDER BY year, month"
 ```
 
 ```json
@@ -44,9 +40,7 @@ curl -s http://localhost:7117/query \
 Captures are real SQL columns, so aggregation works:
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT year, COUNT(*) AS photos FROM photos GROUP BY year"}'
+dirsql query "SELECT year, COUNT(*) AS photos FROM photos GROUP BY year"
 ```
 
 ```json

{dirsql-0.3.72 → dirsql-0.3.73/packages/rust}/docs/howto/define-tables.md

@@ -24,26 +24,12 @@ glob = "posts/**/*.md"
   filesystem facts `dirsql` computes for every file. Facts are opt-in by
   DDL: only the ones you declare become columns.
 
-## 2. Start the server and query
-
-::: code-group
-
-```bash [npm]
-npx dirsql
-```
-
-```bash [PyPI]
-uvx dirsql
-```
-
-:::
+## 2. Query the table
 
 Each matched file is one row:
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT _path, _size FROM posts ORDER BY _path"}'
+dirsql query "SELECT _path, _size FROM posts ORDER BY _path"
 ```
 
 ```json

{dirsql-0.3.72 → dirsql-0.3.73/packages/rust}/docs/howto/extract-from-contents.md

@@ -31,12 +31,8 @@ by every hook.
 
 ## 2. Query the extracted columns
 
-Start the server (`npx dirsql` / `uvx dirsql`) and query:
-
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT title, author, year, _path FROM books ORDER BY year"}'
+dirsql query "SELECT title, author, year, _path FROM books ORDER BY year"
 ```
 
 ```json
@@ -61,9 +57,7 @@ on-file = "jq -c -s '.' {path}"
 ```
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT event, user FROM events"}'
+dirsql query "SELECT event, user FROM events"
 ```
 
 ```json

{dirsql-0.3.72 → dirsql-0.3.73/packages/rust}/docs/howto/load-extension.md

@@ -23,13 +23,10 @@ overrides the init symbol when it doesn't match the filename-derived
 default — `sqlite-vec` is exactly such a case
 ([reference](../reference/config.md#dirsql-extension)).
 
-Start the server (`npx dirsql` / `uvx dirsql`) and the extension's
-functions are callable:
+The extension's functions are callable:
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT vec_version() AS vec_version"}'
+dirsql query "SELECT vec_version() AS vec_version"
 ```
 
 ```json

{dirsql-0.3.72 → dirsql-0.3.73/packages/rust}/docs/howto/search-by-meaning.md

@@ -99,20 +99,14 @@ installed `sqlite_vec` module to its bundled loadable. Naming rules per
 runtime — and the literal-path alternative that works everywhere — are in
 [Load a SQLite extension](./load-extension.md).
 
-## 3. Start the server and ask questions
+## 3. Ask questions
 
-Launch with `sqlite-vec` available to the launcher's environment:
+Run with `sqlite-vec` available to the launcher's environment. The initial
+scan runs `embed.py` once per note, then the query argument goes straight to
+`pre-query`, exactly as a `POST /query` body would:
 
 ```bash
-uvx --with sqlite-vec dirsql
-```
-
-The initial scan runs `embed.py` once per note. Then ask:
-
-```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"q": "how do I cook pasta?"}'
+uvx --with sqlite-vec dirsql query '{"q": "how do I cook pasta?"}'
 ```
 
 ```json
@@ -120,9 +114,7 @@ curl -s http://localhost:7117/query \
 ```
 
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"q": "reviewing code on github"}'
+uvx --with sqlite-vec dirsql query '{"q": "reviewing code on github"}'
 ```
 
 ```json
@@ -133,9 +125,9 @@ Neither question shares a keyword with its top note — "cook" appears
 nowhere in `pasta.md`, "github" nowhere in `branches.md`. The distance
 ranking is doing the work.
 
-Because `pre-query` is set, the request body is *not* the usual
-`{"sql": …}` — the raw body goes to your script, which decides what SQL
-runs ([hook interactions](../reference/http-api.md#hook-interactions)).
+Because `pre-query` is set, the query argument is *not* the usual
+`{"sql": …}` — it goes to your script as-is, which decides what SQL runs
+([hook interactions](../reference/http-api.md#hook-interactions)).
 
 ## Recomputing vs. caching
 

{dirsql-0.3.72/packages/python → dirsql-0.3.73/packages/rust}/docs/howto/skip-files.md

@@ -31,12 +31,8 @@ ignored file never reaches any table — even one whose glob would match it.
 
 ## 2. Confirm what made it in
 
-Start the server (`npx dirsql` / `uvx dirsql`) and check:
-
 ```bash
-curl -s http://localhost:7117/query \
-  -H 'content-type: application/json' \
-  -d '{"sql":"SELECT _path FROM notes ORDER BY _path"}'
+dirsql query "SELECT _path FROM notes ORDER BY _path"
 ```
 
 ```json

{dirsql-0.3.72 → dirsql-0.3.73}/packages/rust/src/cli/execute.rs

@@ -123,7 +123,9 @@ fn parse_sql_body(body: &str) -> Result<String, QueryFailure> {
 /// (`Internal`).
 fn classify_query_error(err: DirSqlError) -> QueryFailure {
     match err {
-        DirSqlError::Core(_) => QueryFailure::BadRequest(err.to_string()),
+        DirSqlError::Core(_) | DirSqlError::WriteForbidden => {
+            QueryFailure::BadRequest(err.to_string())
+        }
         _ => QueryFailure::Internal(err.to_string()),
     }
 }
@@ -237,6 +239,17 @@ mod tests {
         );
     }
 
+    #[test]
+    fn classify_write_forbidden_is_bad_request() {
+        // A rejected write is the caller's fault, exactly like a `Core` SQL
+        // error -> `BadRequest`, not the `Internal` catch-all (issue #444).
+        let failure = classify_query_error(DirSqlError::WriteForbidden);
+        assert!(
+            matches!(failure, QueryFailure::BadRequest(_)),
+            "got: {failure:?}"
+        );
+    }
+
     #[test]
     fn require_ready_fails_unavailable_when_degraded() {
         // The degraded state yields `Unavailable` carrying the diagnostic