dirsql 0.4.67 → 0.4.68

package/docs/getting-started.md

@@ -68,11 +68,11 @@ this directory anyway — from inside `my-notes`, run one command:
 ::: code-group
 
 ```bash [npm]
-npx dirsql "SELECT COUNT(*) AS files FROM './'"
+npx dirsql "SELECT COUNT(*) AS files FROM './**'"
 ```
 
 ```bash [PyPI]
-uvx dirsql "SELECT COUNT(*) AS files FROM './'"
+uvx dirsql "SELECT COUNT(*) AS files FROM './**'"
 ```
 
 :::
@@ -91,10 +91,11 @@ files
 Three files, three rows. That one command scanned the directory, handed
 SQLite one row per file, ran your SQL, and printed the answer.
 
-There is no named table here — you never declared one. `'./'` is a
+There is no named table here — you never declared one. `'./**'` is a
 [path-table](./reference/path-tables.md): a quoted path written where a table
-name goes. `'./'` means everything under the directory you ran the command
-in. The path *is* the query.
+name goes. `'./**'` means every file under the directory you ran the command
+in, at any depth; `'./'` alone would list only the files directly inside it,
+like `ls`. The path *is* the query.
 
 ## 3. Select some columns
 
@@ -105,11 +106,11 @@ pretty-print. Ask for two columns instead of a count:
 ::: code-group
 
 ```bash [npm]
-npx dirsql query "SELECT path, size FROM './' ORDER BY path" | jq
+npx dirsql query "SELECT path, size FROM './**' ORDER BY path" | jq
 ```
 
 ```bash [PyPI]
-uvx dirsql query "SELECT path, size FROM './' ORDER BY path" | jq
+uvx dirsql query "SELECT path, size FROM './**' ORDER BY path" | jq
 ```
 
 :::

package/docs/howto/query-without-config.md

@@ -67,5 +67,5 @@ why indexes belong to only one of them, are in
 - Paths outside the root resolve too — `'/var/log/*.log'`, `'../notes'`,
   `'~/notes/*.md'` — reporting absolute paths
   ([path-tables reference](../reference/path-tables.md#paths-outside-the-index-root)).
-- `node_modules/` and `.git/` are skipped by default so a bare `'./'` does not
-  drown in machinery ([skip rules](../reference/path-tables.md#skip-rules)).
+- `node_modules/` and `.git/` are skipped by default so a bare `'./**'` does
+  not drown in machinery ([skip rules](../reference/path-tables.md#skip-rules)).

package/docs/reference/cli.md

@@ -88,7 +88,7 @@ front.
 ### Output format
 
 Rows go where they are useful: a **table** when stdout is a terminal, the
-**JSON array** when it is piped or redirected. `SELECT * FROM './'` in a
+**JSON array** when it is piped or redirected. `SELECT * FROM './**'` in a
 5000-file tree should not put a 5000-element JSON array in front of a person,
 and `dirsql "…" | jq` should not have to parse a table.
 
@@ -283,7 +283,7 @@ curl -s localhost:7117/query -H 'content-type: application/json' \
 ```
 
 Earlier versions served an implicit table named `files` here. It is gone; a
-`SELECT ... FROM files` with no config now fails and points at `FROM './'`.
+`SELECT ... FROM files` with no config now fails and points at `FROM './**'`.
 
 Passing a config with `-c` fully overrules this default. A `-c` naming a file
 that does not exist is an error (not a fallback to the default); a config that
@@ -403,8 +403,8 @@ takes, with the same `auto` default. A one-shot query is usually piped, so
 ## `dirsql init`
 
 Writes a starter `.dirsql.toml` as a scaffold to edit. It does **not**
-duplicate the zero-config floor (`SELECT * FROM './'` already lists every file
-with no config); instead it shows the **escalation**: one named `[[table]]`
+duplicate the zero-config floor (`SELECT * FROM './**'` already lists every
+file with no config); instead it shows the **escalation**: one named `[[table]]`
 with a glob, a schema, and a real `on-file` hook that pulls structured rows
 out of your files.
 

package/docs/reference/config.md

@@ -396,7 +396,7 @@ SDKs raise/reject) when:
 - A `[[table]]` entry omits `on-file` (or it is empty/whitespace). The error
   names the offending glob and points at the fix:
 
-  > `[[table]] '**/*.md' has no on-file hook, so every row would be all-NULL. Add an `on-file` hook that emits the columns, or, for stat columns with no code, query the path directly: `FROM './'``
+  > `[[table]] '**/*.md' has no on-file hook, so every row would be all-NULL. Add an `on-file` hook that emits the columns, or, for stat columns with no code, query the path directly: `FROM './**'``
 
 - A `[[dirsql.extension]]` entry omits `path`, or `path` is empty.
 - A `[[dirsql.function]]` entry omits `name`, `command`, or `args` (or

package/docs/reference/path-tables.md

@@ -35,14 +35,16 @@ Two consequences follow directly:
 A `./` path is relative to the **index root** — the directory dirsql is
 indexing, not your shell's working directory.
 
-**Directories are recursive by default.** Naming a directory scans everything
-beneath it; the non-recursive form is spelled explicitly with `*`.
+**A directory name is one level, like `ls`.** Naming a directory lists the
+files directly inside it and no deeper; `*` matches one level and `**` any
+depth, as in the shell.
 
 | You write | dirsql scans |
 | --- | --- |
-| `'./'` | every file under the index root, recursively |
-| `'./docs'` | every file under `docs/`, recursively |
-| `'./*'` | files directly inside the index root, and no deeper |
+| `'./'` | files directly inside the index root, and no deeper |
+| `'./docs'`, `'./docs/'` | files directly inside `docs/` |
+| `'./*'` | the same as `'./'` |
+| `'./**'` | every file under the index root, recursively |
 | `'./docs/*.md'` | markdown files directly inside `docs/` |
 | `'./docs/**/*.md'` | markdown files at any depth under `docs/` |
 | `'./notes/today.md'` | exactly that one file — one file is one row |
@@ -87,6 +89,7 @@ Three other prefixes resolve, with their usual shell meanings:
 | `'../notes'` | relative to the index root's parent |
 | `'~/notes/*.md'` | relative to your home directory |
 
+A directory named this way is one level too; `'../notes/**'` descends.
 `..` is folded out textually, not followed through symlinks, so the directory
 scanned is a function of the string you wrote.
 
@@ -216,7 +219,7 @@ A path-table scan applies the same [`ignore`](/reference/config) patterns your
 declared tables use — matched against root-relative paths under the same
 [glob rule](/reference/config#glob-rule) as the path itself, `*` one level and
 `**` any depth — plus two built-in defaults so a zero-config
-`SELECT * FROM './'` does not drown in machinery:
+`SELECT * FROM './**'` does not drown in machinery:
 
 - `**/node_modules/**`
 - `**/.git/**`
@@ -246,7 +249,7 @@ Skip rules are judged from the directory the scan starts in, so pointing at a
 skipped directory — built-in or gitignored — still scans it:
 
 ```sql
-SELECT path FROM './';                     -- no node_modules rows
+SELECT path FROM './**';                   -- no node_modules rows
 SELECT path FROM './node_modules/*/package.json';  -- scans it anyway
 SELECT path FROM './dist';                 -- scans dist/ even when gitignored
 ```

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dirsql",
-  "version": "0.4.67",
+  "version": "0.4.68",
   "description": "Ephemeral SQL index over a local directory",
   "license": "MIT",
   "repository": "https://github.com/thekevinscott/dirsql",
@@ -221,10 +221,10 @@
     ]
   },
   "optionalDependencies": {
-    "@dirsql/lib-linux-x64-gnu": "0.4.67",
-    "@dirsql/lib-linux-arm64-gnu": "0.4.67",
-    "@dirsql/lib-darwin-x64": "0.4.67",
-    "@dirsql/lib-darwin-arm64": "0.4.67",
-    "@dirsql/lib-win32-x64-msvc": "0.4.67"
+    "@dirsql/lib-linux-x64-gnu": "0.4.68",
+    "@dirsql/lib-linux-arm64-gnu": "0.4.68",
+    "@dirsql/lib-darwin-x64": "0.4.68",
+    "@dirsql/lib-darwin-arm64": "0.4.68",
+    "@dirsql/lib-win32-x64-msvc": "0.4.68"
   }
 }