dirsql 0.4.82__tar.gz → 0.4.84__tar.gz

{dirsql-0.4.82 → dirsql-0.4.84}/Cargo.lock

@@ -552,7 +552,7 @@ checksum = "6184e33543162437515c2e2b48714794e37845ec9851711914eec9d308f6ebe8"
 
 [[package]]
 name = "dirsql"
-version = "0.4.82"
+version = "0.4.84"
 dependencies = [
  "assert_cmd",
  "axum",
@@ -602,7 +602,7 @@ dependencies = [
 
 [[package]]
 name = "dirsql-py-ext"
-version = "0.4.82"
+version = "0.4.84"
 dependencies = [
  "dirsql",
  "pyo3",

{dirsql-0.4.82 → dirsql-0.4.84}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dirsql
-Version: 0.4.82
+Version: 0.4.84
 Requires-Dist: bin-shim>=0.1
 Summary: Ephemeral SQL index over a local directory
 Keywords: sql,filesystem,directory,sqlite,index

{dirsql-0.4.82 → dirsql-0.4.84}/dirsql/_async.py

@@ -2,6 +2,7 @@
 
 import asyncio
 import os
+import weakref
 
 from dirsql._dirsql import DirSQL as _RustDirSQL
 from dirsql.resolve_configs_extension_specs import resolve_configs_extension_specs
@@ -9,13 +10,18 @@ from dirsql.resolve_extension import resolve_extension_path
 
 
 class _WatchStream:
-    """Async iterator that polls for file events."""
+    """Async iterator of file events.
+
+    Every stream on one ``DirSQL`` receives every event observed after it
+    was created: one shared poll fills the buffer of each live stream.
+    """
 
     def __init__(self, owner):
         self._owner = owner
         self._db = None
         self._started = False
         self._buffer = []
+        owner._watch_streams.add(self)
 
     def __aiter__(self):
         return self
@@ -29,14 +35,22 @@ class _WatchStream:
             await asyncio.to_thread(db._start_watcher)
             self._started = True
 
+        owner = self._owner
+        while not self._buffer:
+            poll = owner._watch_poll
+            if poll is None or poll.done():
+                poll = owner._watch_poll = asyncio.ensure_future(self._poll())
+            # Shielded so a cancelled consumer cannot drop a batch that the
+            # other streams are still waiting on.
+            await asyncio.shield(poll)
+        return self._buffer.pop(0)
+
+    async def _poll(self):
         db = self._db
         assert db is not None
-        while True:
-            if self._buffer:
-                return self._buffer.pop(0)
-            events = await asyncio.to_thread(db._poll_events, 200)
-            if events:
-                self._buffer.extend(events)
+        events = await asyncio.to_thread(db._poll_events, 200)
+        for stream in list(self._owner._watch_streams):
+            stream._buffer.extend(events)
 
 
 class DirSQL:
@@ -107,6 +121,8 @@ class DirSQL:
         self._db = None
         self._ready_event = asyncio.Event()
         self._init_error = None
+        self._watch_streams = weakref.WeakSet()
+        self._watch_poll = None
         self._task = asyncio.ensure_future(self._init_bg())
 
     async def _init_bg(self):
@@ -218,5 +234,9 @@ class DirSQL:
         before an explicit ``await db.ready()`` waits for the background scan
         (and surfaces any initialization error) instead of failing on a
         still-``None`` ``_db``.
+
+        Each call returns an independent stream, and every stream receives
+        every event observed after it was created, so several consumers
+        (one per client, say) can share one instance.
         """
         return _WatchStream(self)

{dirsql-0.4.82/packages/rust → dirsql-0.4.84}/docs/howto/write-a-plugin.md

@@ -62,7 +62,9 @@ and [`ignore`](../reference/config.md#dirsql-keys).
 There are **no plugin-specific keys and no plugin-specific restrictions**. The
 config schema is content-only: the index root and persistence are
 [runner-owned](../reference/config.md#dirsql-keys) — the root is the directory
-`dirsql` is run from (or an SDK's explicit `root`), persistence is the
+`dirsql` is run from (or an SDK's explicit `root`) and governs path-tables,
+while a fragment's own `[[table]]` globs anchor at the fragment's directory
+(see [glob anchor](../reference/config.md#glob-anchor)); persistence is the
 `--persist [PATH]` flag — decided by whoever runs `dirsql`, never by a config
 file, so a plugin has nothing to say about them. Whatever you can put in your
 own `.dirsql.toml`, a plugin can put in its fragment, and vice-versa.
@@ -86,11 +88,10 @@ matter most for a published plugin:
 - **A hook runs in its declaring config's directory.** For a plugin that is
   the installed fragment's directory — inside **site-packages**. That is a
   read-only, shared location: **run from it, never write to it.** Read the
-  matched files from the absolute paths the hook appends as arguments, and use
-  [`{root}`](../reference/hooks.md#on-file) to reach the user's project
-  directory. Write any cache to `{root}` or a real cache dir,
-  never next to the fragment.
-- **The paths are absolute and `{root}` is the index root**, so a command is
+  matched files from the absolute paths the hook appends as arguments. Write any cache to a real cache dir, never next to
+  the fragment.
+- **The paths are absolute and `{root}` is the table's glob anchor** (the
+  fragment's directory, or the literal prefix of an absolute / `~/` glob), so a command is
   self-sufficient from any working directory — it works whether the plugin
   lives in the project or in site-packages.
 

{dirsql-0.4.82 → dirsql-0.4.84}/docs/reference/cli.md

@@ -244,7 +244,7 @@ Config flags are subcommand-local: pass them after `server`
 
 | Flag | Default | Description |
 |---|---|---|
-| `-c, --config <path>` | none | Path to a [config file](./config.md). **Repeatable** (`-c a -c b`): the configs load and merge in argv order — see [Composing multiple configs](./config.md#composing-multiple-configs). The index is always rooted at the **invocation directory** (the current working directory), regardless of where a config lives — so `--config /elsewhere/.dirsql.toml` still indexes the directory you ran `dirsql server` from. With none given, **no named tables are defined** — query the filesystem with a [path-table](./path-tables.md) (`FROM './'`). A `./.dirsql.toml` on disk is **not** auto-loaded; pass it explicitly. A `-c` naming a file that does not exist is an [error](#degraded-mode). |
+| `-c, --config <path>` | none | Path to a [config file](./config.md). **Repeatable** (`-c a -c b`): the configs load and merge in argv order — see [Composing multiple configs](./config.md#composing-multiple-configs). The index root is the **invocation directory** (the current working directory) and governs path-tables; a config's `[[table]]` globs anchor at **that config's own directory** (see [glob anchor](./config.md#glob-anchor)), so `--config /elsewhere/.dirsql.toml` indexes `/elsewhere`, from any working directory. With none given, **no named tables are defined** — query the filesystem with a [path-table](./path-tables.md) (`FROM './'`). A `./.dirsql.toml` on disk is **not** auto-loaded; pass it explicitly. A `-c` naming a file that does not exist is an [error](#degraded-mode). |
 | `--host <addr>` | `localhost` | Bind address. |
 | `--port <n>` | `7117` | TCP port to bind. |
 | `--persist [<path>]` | off | Keep the SQLite index on disk between runs so a restart only re-parses files that actually changed. Bare `--persist` caches at `<root>/.dirsql/cache.db`; `--persist <path>` caches at `<path>`. Off by default (the index is ephemeral). Also available on [`dirsql query`](#dirsql-query). See [Keep the index across restarts](../howto/persist.md). |

{dirsql-0.4.82/packages/rust → dirsql-0.4.84}/docs/reference/config.md

@@ -14,17 +14,19 @@ with none given [no named tables](./cli.md#configless-mode) are defined (a
 `./.dirsql.toml` on disk is **not** auto-loaded). The [SDKs](./sdk.md) load a
 config via the `config` constructor parameter.
 
-**Path resolution.** Relative paths in the config (`[[dirsql.extension]]`
-`path`) resolve against the config file's parent
-directory. The **index root is not a config concern** — it is decided by the
-runner (the CLI's invocation directory, or an SDK's explicit root), never by
-the config file's location. See [`--config`](./cli.md#flags).
+**Path resolution.** A path written in a config resolves against the config
+file's parent directory: a `[[table]]` `glob` (see [anchoring](#glob-anchor)),
+`ignore`, and `[[dirsql.extension]]` `path`. A config therefore works from any
+working directory. The **index root is not a config concern** — it is decided
+by the runner (the CLI's invocation directory, or an SDK's explicit root) and
+governs only path-tables and programmatic tables. See
+[`--config`](./cli.md#flags).
 
 ## `[dirsql]` keys
 
 | Key | Type | Default | Description |
 |---|---|---|---|
-| `ignore` | array of strings | `[]` | Glob patterns matched against root-relative paths, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Matched files are skipped entirely — excluded from the initial scan and from watch events. |
+| `ignore` | array of strings | `[]` | Glob patterns matched against paths relative to the config file's directory, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. They apply only to this config's `[[table]]` entries (not to path-tables, and not to another config's tables). Matched files are skipped entirely — excluded from the initial scan and from watch events. |
 
 There is no timeout key. `on-file` hook runs are unbounded; to bound one, wrap
 its command in `timeout(1)` (see [Command hooks](./hooks.md#bounding-a-hook)).
@@ -230,7 +232,7 @@ what its required `on-file` command emits — dirsql injects nothing (see
 |---|---|---|
 | `name` | yes | The table's SQL name — the name you query it by. Declared, never derived from `ddl`: dirsql does not read the DDL text. The `ddl` must create a table by this name; if it doesn't, loading fails. |
 | `ddl` | yes | A SQL batch, run verbatim — any number of statements. It must create a table called `name`; that table holds the file rows, and only the columns it declares are kept (keys the `on-file` command emits that are not declared are dropped). The rest of the batch is yours: indexes, virtual tables, triggers. See [Batch `ddl`](#batch-ddl). |
-| `glob` | yes | Glob pattern matched against root-relative paths, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Every table whose glob matches a file receives that file's rows — a file can populate multiple tables. A `{name}` segment is rewritten to `*` (it matches one path segment but captures nothing). |
+| `glob` | yes | Glob pattern, [anchored](#glob-anchor) at the config file's directory, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Every table whose glob matches a file receives that file's rows — a file can populate multiple tables. A `{name}` segment is rewritten to `*` (it matches one path segment but captures nothing). |
 | `on-file` | **yes** | A command run once per table, with every matched file's absolute path appended as a trailing argument; its stdout (one JSON array of row objects) is the table's rows. Must be non-empty. A `[[table]]` with no `on-file` is a load error (see [parse errors](#parse-errors)). See [Command hooks](./hooks.md#on-file). |
 | `strict` | no (default `false`) | When `true`, rows whose keys do not exactly match the declared columns are rejected with an error: extra keys error, and every declared column must be supplied by the `on-file` output. When `false`, extra keys are dropped and missing columns become `NULL`. |
 
@@ -256,6 +258,26 @@ on-file = "uv run python extract_papers.py"
 strict  = true
 ```
 
+### Glob anchor
+
+A table's `glob` is matched beneath its **anchor**, never the index root:
+
+| `glob` starts with | Anchor |
+|---|---|
+| nothing special, or `./` | the config file's directory |
+| `/` (or a drive / UNC root) | the literal directory chain before the first glob character |
+| `~/` | your home directory, then the literal chain |
+| `../` | resolved against the config file's directory, then the literal chain |
+
+So `glob = "projects/*/*.jsonl"` in `~/.claude/.dirsql.toml` indexes
+`~/.claude/projects` from any working directory, and a shared config elsewhere
+writes `glob = "~/.claude/projects/*/*.jsonl"`. A table's `path` and `dir`
+columns, `{root}`, and `ignore` are all relative to its anchor.
+
+A table whose glob matches no files prints
+`dirsql: table 'sessions': glob 'projects/*/*.jsonl' matched no files under <anchor>`
+to stderr; the exit code is unchanged. Path-tables and programmatic tables do not warn.
+
 ### Batch `ddl`
 
 `ddl` is handed to SQLite whole, so a table declaration is not limited to one
@@ -346,7 +368,7 @@ dirsql -c ./.dirsql.toml -c ~/team/embeddings.toml -c ./local.toml
 
 The configs load and merge in **argv order**:
 
-- **`[[table]]`, `ignore`, `[[dirsql.extension]]`, and `[[dirsql.function]]`
+- **`[[table]]`, `[[dirsql.extension]]`, and `[[dirsql.function]]`
   entries accumulate** across all configs, in order.
 - **Each config's `on-file` hooks and `[[dirsql.function]]` workers run from
   that config file's own directory** — so a relative command like
@@ -360,7 +382,8 @@ The configs load and merge in **argv order**:
   silent last-writer-wins.
 
 The index [root](./cli.md#flags) is the invocation directory regardless of where
-any config lives. With no `-c`, [no named tables](./cli.md#configless-mode) are
+any config lives; each config's `[[table]]` globs anchor at that config's own
+directory, and its `ignore` applies to its own tables only. With no `-c`, [no named tables](./cli.md#configless-mode) are
 defined (no `./.dirsql.toml` auto-discovery); a single `-c` behaves exactly as
 before.
 

{dirsql-0.4.82 → dirsql-0.4.84}/docs/reference/hooks.md

@@ -42,7 +42,8 @@ relative paths in the command resolve predictably regardless of where
 `dirsql` was launched. A command named by the `--on-file` flag has no config
 file: it runs in the **index root**, the directory `dirsql query` was run in,
 which is also the directory a `./` path-table is relative to. In both forms
-`{root}` is the index root. The command inherits `dirsql`'s environment, so
+`{root}` is where the table's glob is anchored: the index root for `--on-file`,
+the [glob anchor](./config.md#glob-anchor) for a `[[table]]`. The command inherits `dirsql`'s environment, so
 tools like `uvx --with …` / `npx …` resolve their dependencies as usual.
 
 ### stdout protocol
@@ -143,7 +144,7 @@ the path or stat metadata emits it (it has the paths).
 
 | Placeholder | Value |
 |---|---|
-| `{root}` | The index root directory. Derive a root-relative path with `relpath(path, {root})`. |
+| `{root}` | The directory the table's glob is anchored at (the index root for `--on-file`; the config file's directory, or the literal prefix of an absolute / `~/` glob, for a `[[table]]`). Derive an anchor-relative path with `relpath(path, {root})`. |
 
 The matched files' **absolute** paths are not placeholders: they are appended
 to the command as trailing arguments, after everything written in the

{dirsql-0.4.82 → dirsql-0.4.84}/docs/reference/sdk.md

@@ -98,7 +98,9 @@ DirSQL::builder()
 
 Creates a SQLite index over a directory. The index root is the explicit
 `root` when given, else the **process cwd** — the `config` file's location
-never sets the root.
+never sets the root. A config's `[[table]]` globs anchor at the config file's
+own directory instead (see [glob anchor](./config.md#glob-anchor)); `root`
+governs programmatic tables and path-tables.
 
 Constructing with **neither a `config` nor programmatic `tables`** defines
 **no named tables** — the same as the CLI with no
@@ -127,7 +129,9 @@ shortcut was removed in #603 — use
   entries are appended after any programmatic `tables`; its `ignore`
   patterns and `[[dirsql.extension]]` entries are appended likewise. The
   config file does **not** set the index root: with no explicit `root`, the
-  index roots at the process cwd. **Multiple configs merge in order** on
+  index roots at the process cwd. Its `[[table]]` globs anchor at the config
+  file's directory (or at the literal prefix of an absolute / `~/` glob), not
+  at `root`; its `ignore` applies to its own tables only. **Multiple configs merge in order** on
   every SDK — **Python** `config` accepts a `str` or a `list[str]`, the
   **Rust** builder's `.config()` is repeatable (call it once per file), and
   **TypeScript** `config` accepts a `string` or a `string[]`; the configs
@@ -297,6 +301,10 @@ under the root. The watcher starts on first iteration (Python/TypeScript)
 or at the `watch()` call (Rust). The stream never terminates on its own;
 stop consuming it to stop.
 
+Python: each `watch()` call returns an independent stream, and every stream
+on one instance receives every event observed after it was created, so
+several consumers (one per client, say) can share one instance.
+
 Rust: `watch()` may be called once per instance and is mutually exclusive
 with the polling API below — mixing them returns an error, since both drain
 the same underlying filesystem watcher.

{dirsql-0.4.82 → dirsql-0.4.84}/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.4.82"
+version = "0.4.84"
 # abi3 note: the `abi3-py310` pyo3 feature (below) builds ONE stable-ABI
 # `cp310-abi3` wheel per platform that loads on every CPython >= 3.10
 # (matching `pyproject.toml`'s `requires-python = ">=3.10"`), instead of

dirsql-0.4.84/packages/python/changelog.d/2026-10-06-config-globs-anchor-at-the-config.md

@@ -0,0 +1,3 @@
+**Changed**
+
+- **A config `[[table]]` `glob` now anchors at its config file's directory, not the index root.** `glob = "projects/*/*.jsonl"` in `~/.claude/.dirsql.toml` indexes `~/.claude/projects` from any working directory. A glob may also start with `/`, `~/` or `../` (the path-table prefix grammar): it anchors at the literal directory chain before its first glob character. `{root}` in an `on-file` command, a table's `path`/`dir` columns, and `ignore` are all relative to the table's anchor. A config's `ignore` now applies to that config's tables only, no longer to path-tables or to other configs' tables. The index root (cwd, or `root=`) is unchanged and still governs path-tables and programmatic tables. (#1232)

dirsql-0.4.84/packages/python/changelog.d/2026-10-06-watch-broadcast.md

@@ -0,0 +1,3 @@
+**Fixed**
+
+- **Every `DirSQL.watch()` stream on one instance now receives every event.** Two or more streams (for example one per connected client) previously split the events between them; now each stream gets every event observed after it was created. (#1397)

dirsql-0.4.84/packages/python/changelog.d/2026-10-06-zero-match-config-table-warning.md

@@ -0,0 +1,3 @@
+**Added**
+
+- **A config `[[table]]` whose glob matches no files now prints a warning to stderr.** `dirsql: table 'sessions': glob 'projects/*/*.jsonl' matched no files under /home/u/.claude` names the table, the glob and the directory it was matched under, so a glob that silently indexes nothing is visible. The exit code is unchanged, and path-tables and programmatic tables do not warn. (#1232)

{dirsql-0.4.82 → dirsql-0.4.84/packages/python}/docs/howto/write-a-plugin.md

@@ -62,7 +62,9 @@ and [`ignore`](../reference/config.md#dirsql-keys).
 There are **no plugin-specific keys and no plugin-specific restrictions**. The
 config schema is content-only: the index root and persistence are
 [runner-owned](../reference/config.md#dirsql-keys) — the root is the directory
-`dirsql` is run from (or an SDK's explicit `root`), persistence is the
+`dirsql` is run from (or an SDK's explicit `root`) and governs path-tables,
+while a fragment's own `[[table]]` globs anchor at the fragment's directory
+(see [glob anchor](../reference/config.md#glob-anchor)); persistence is the
 `--persist [PATH]` flag — decided by whoever runs `dirsql`, never by a config
 file, so a plugin has nothing to say about them. Whatever you can put in your
 own `.dirsql.toml`, a plugin can put in its fragment, and vice-versa.
@@ -86,11 +88,10 @@ matter most for a published plugin:
 - **A hook runs in its declaring config's directory.** For a plugin that is
   the installed fragment's directory — inside **site-packages**. That is a
   read-only, shared location: **run from it, never write to it.** Read the
-  matched files from the absolute paths the hook appends as arguments, and use
-  [`{root}`](../reference/hooks.md#on-file) to reach the user's project
-  directory. Write any cache to `{root}` or a real cache dir,
-  never next to the fragment.
-- **The paths are absolute and `{root}` is the index root**, so a command is
+  matched files from the absolute paths the hook appends as arguments. Write any cache to a real cache dir, never next to
+  the fragment.
+- **The paths are absolute and `{root}` is the table's glob anchor** (the
+  fragment's directory, or the literal prefix of an absolute / `~/` glob), so a command is
   self-sufficient from any working directory — it works whether the plugin
   lives in the project or in site-packages.
 

{dirsql-0.4.82/packages/rust → dirsql-0.4.84/packages/python}/docs/reference/cli.md

@@ -244,7 +244,7 @@ Config flags are subcommand-local: pass them after `server`
 
 | Flag | Default | Description |
 |---|---|---|
-| `-c, --config <path>` | none | Path to a [config file](./config.md). **Repeatable** (`-c a -c b`): the configs load and merge in argv order — see [Composing multiple configs](./config.md#composing-multiple-configs). The index is always rooted at the **invocation directory** (the current working directory), regardless of where a config lives — so `--config /elsewhere/.dirsql.toml` still indexes the directory you ran `dirsql server` from. With none given, **no named tables are defined** — query the filesystem with a [path-table](./path-tables.md) (`FROM './'`). A `./.dirsql.toml` on disk is **not** auto-loaded; pass it explicitly. A `-c` naming a file that does not exist is an [error](#degraded-mode). |
+| `-c, --config <path>` | none | Path to a [config file](./config.md). **Repeatable** (`-c a -c b`): the configs load and merge in argv order — see [Composing multiple configs](./config.md#composing-multiple-configs). The index root is the **invocation directory** (the current working directory) and governs path-tables; a config's `[[table]]` globs anchor at **that config's own directory** (see [glob anchor](./config.md#glob-anchor)), so `--config /elsewhere/.dirsql.toml` indexes `/elsewhere`, from any working directory. With none given, **no named tables are defined** — query the filesystem with a [path-table](./path-tables.md) (`FROM './'`). A `./.dirsql.toml` on disk is **not** auto-loaded; pass it explicitly. A `-c` naming a file that does not exist is an [error](#degraded-mode). |
 | `--host <addr>` | `localhost` | Bind address. |
 | `--port <n>` | `7117` | TCP port to bind. |
 | `--persist [<path>]` | off | Keep the SQLite index on disk between runs so a restart only re-parses files that actually changed. Bare `--persist` caches at `<root>/.dirsql/cache.db`; `--persist <path>` caches at `<path>`. Off by default (the index is ephemeral). Also available on [`dirsql query`](#dirsql-query). See [Keep the index across restarts](../howto/persist.md). |

{dirsql-0.4.82 → dirsql-0.4.84/packages/python}/docs/reference/config.md

@@ -14,17 +14,19 @@ with none given [no named tables](./cli.md#configless-mode) are defined (a
 `./.dirsql.toml` on disk is **not** auto-loaded). The [SDKs](./sdk.md) load a
 config via the `config` constructor parameter.
 
-**Path resolution.** Relative paths in the config (`[[dirsql.extension]]`
-`path`) resolve against the config file's parent
-directory. The **index root is not a config concern** — it is decided by the
-runner (the CLI's invocation directory, or an SDK's explicit root), never by
-the config file's location. See [`--config`](./cli.md#flags).
+**Path resolution.** A path written in a config resolves against the config
+file's parent directory: a `[[table]]` `glob` (see [anchoring](#glob-anchor)),
+`ignore`, and `[[dirsql.extension]]` `path`. A config therefore works from any
+working directory. The **index root is not a config concern** — it is decided
+by the runner (the CLI's invocation directory, or an SDK's explicit root) and
+governs only path-tables and programmatic tables. See
+[`--config`](./cli.md#flags).
 
 ## `[dirsql]` keys
 
 | Key | Type | Default | Description |
 |---|---|---|---|
-| `ignore` | array of strings | `[]` | Glob patterns matched against root-relative paths, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Matched files are skipped entirely — excluded from the initial scan and from watch events. |
+| `ignore` | array of strings | `[]` | Glob patterns matched against paths relative to the config file's directory, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. They apply only to this config's `[[table]]` entries (not to path-tables, and not to another config's tables). Matched files are skipped entirely — excluded from the initial scan and from watch events. |
 
 There is no timeout key. `on-file` hook runs are unbounded; to bound one, wrap
 its command in `timeout(1)` (see [Command hooks](./hooks.md#bounding-a-hook)).
@@ -230,7 +232,7 @@ what its required `on-file` command emits — dirsql injects nothing (see
 |---|---|---|
 | `name` | yes | The table's SQL name — the name you query it by. Declared, never derived from `ddl`: dirsql does not read the DDL text. The `ddl` must create a table by this name; if it doesn't, loading fails. |
 | `ddl` | yes | A SQL batch, run verbatim — any number of statements. It must create a table called `name`; that table holds the file rows, and only the columns it declares are kept (keys the `on-file` command emits that are not declared are dropped). The rest of the batch is yours: indexes, virtual tables, triggers. See [Batch `ddl`](#batch-ddl). |
-| `glob` | yes | Glob pattern matched against root-relative paths, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Every table whose glob matches a file receives that file's rows — a file can populate multiple tables. A `{name}` segment is rewritten to `*` (it matches one path segment but captures nothing). |
+| `glob` | yes | Glob pattern, [anchored](#glob-anchor) at the config file's directory, under the [one glob rule](#glob-rule): `*` matches one level, `**` any depth. Every table whose glob matches a file receives that file's rows — a file can populate multiple tables. A `{name}` segment is rewritten to `*` (it matches one path segment but captures nothing). |
 | `on-file` | **yes** | A command run once per table, with every matched file's absolute path appended as a trailing argument; its stdout (one JSON array of row objects) is the table's rows. Must be non-empty. A `[[table]]` with no `on-file` is a load error (see [parse errors](#parse-errors)). See [Command hooks](./hooks.md#on-file). |
 | `strict` | no (default `false`) | When `true`, rows whose keys do not exactly match the declared columns are rejected with an error: extra keys error, and every declared column must be supplied by the `on-file` output. When `false`, extra keys are dropped and missing columns become `NULL`. |
 
@@ -256,6 +258,26 @@ on-file = "uv run python extract_papers.py"
 strict  = true
 ```
 
+### Glob anchor
+
+A table's `glob` is matched beneath its **anchor**, never the index root:
+
+| `glob` starts with | Anchor |
+|---|---|
+| nothing special, or `./` | the config file's directory |
+| `/` (or a drive / UNC root) | the literal directory chain before the first glob character |
+| `~/` | your home directory, then the literal chain |
+| `../` | resolved against the config file's directory, then the literal chain |
+
+So `glob = "projects/*/*.jsonl"` in `~/.claude/.dirsql.toml` indexes
+`~/.claude/projects` from any working directory, and a shared config elsewhere
+writes `glob = "~/.claude/projects/*/*.jsonl"`. A table's `path` and `dir`
+columns, `{root}`, and `ignore` are all relative to its anchor.
+
+A table whose glob matches no files prints
+`dirsql: table 'sessions': glob 'projects/*/*.jsonl' matched no files under <anchor>`
+to stderr; the exit code is unchanged. Path-tables and programmatic tables do not warn.
+
 ### Batch `ddl`
 
 `ddl` is handed to SQLite whole, so a table declaration is not limited to one
@@ -346,7 +368,7 @@ dirsql -c ./.dirsql.toml -c ~/team/embeddings.toml -c ./local.toml
 
 The configs load and merge in **argv order**:
 
-- **`[[table]]`, `ignore`, `[[dirsql.extension]]`, and `[[dirsql.function]]`
+- **`[[table]]`, `[[dirsql.extension]]`, and `[[dirsql.function]]`
   entries accumulate** across all configs, in order.
 - **Each config's `on-file` hooks and `[[dirsql.function]]` workers run from
   that config file's own directory** — so a relative command like
@@ -360,7 +382,8 @@ The configs load and merge in **argv order**:
   silent last-writer-wins.
 
 The index [root](./cli.md#flags) is the invocation directory regardless of where
-any config lives. With no `-c`, [no named tables](./cli.md#configless-mode) are
+any config lives; each config's `[[table]]` globs anchor at that config's own
+directory, and its `ignore` applies to its own tables only. With no `-c`, [no named tables](./cli.md#configless-mode) are
 defined (no `./.dirsql.toml` auto-discovery); a single `-c` behaves exactly as
 before.
 

{dirsql-0.4.82/packages/rust → dirsql-0.4.84/packages/python}/docs/reference/hooks.md

@@ -42,7 +42,8 @@ relative paths in the command resolve predictably regardless of where
 `dirsql` was launched. A command named by the `--on-file` flag has no config
 file: it runs in the **index root**, the directory `dirsql query` was run in,
 which is also the directory a `./` path-table is relative to. In both forms
-`{root}` is the index root. The command inherits `dirsql`'s environment, so
+`{root}` is where the table's glob is anchored: the index root for `--on-file`,
+the [glob anchor](./config.md#glob-anchor) for a `[[table]]`. The command inherits `dirsql`'s environment, so
 tools like `uvx --with …` / `npx …` resolve their dependencies as usual.
 
 ### stdout protocol
@@ -143,7 +144,7 @@ the path or stat metadata emits it (it has the paths).
 
 | Placeholder | Value |
 |---|---|
-| `{root}` | The index root directory. Derive a root-relative path with `relpath(path, {root})`. |
+| `{root}` | The directory the table's glob is anchored at (the index root for `--on-file`; the config file's directory, or the literal prefix of an absolute / `~/` glob, for a `[[table]]`). Derive an anchor-relative path with `relpath(path, {root})`. |
 
 The matched files' **absolute** paths are not placeholders: they are appended
 to the command as trailing arguments, after everything written in the

{dirsql-0.4.82/packages/rust → dirsql-0.4.84/packages/python}/docs/reference/sdk.md

@@ -98,7 +98,9 @@ DirSQL::builder()
 
 Creates a SQLite index over a directory. The index root is the explicit
 `root` when given, else the **process cwd** — the `config` file's location
-never sets the root.
+never sets the root. A config's `[[table]]` globs anchor at the config file's
+own directory instead (see [glob anchor](./config.md#glob-anchor)); `root`
+governs programmatic tables and path-tables.
 
 Constructing with **neither a `config` nor programmatic `tables`** defines
 **no named tables** — the same as the CLI with no
@@ -127,7 +129,9 @@ shortcut was removed in #603 — use
   entries are appended after any programmatic `tables`; its `ignore`
   patterns and `[[dirsql.extension]]` entries are appended likewise. The
   config file does **not** set the index root: with no explicit `root`, the
-  index roots at the process cwd. **Multiple configs merge in order** on
+  index roots at the process cwd. Its `[[table]]` globs anchor at the config
+  file's directory (or at the literal prefix of an absolute / `~/` glob), not
+  at `root`; its `ignore` applies to its own tables only. **Multiple configs merge in order** on
   every SDK — **Python** `config` accepts a `str` or a `list[str]`, the
   **Rust** builder's `.config()` is repeatable (call it once per file), and
   **TypeScript** `config` accepts a `string` or a `string[]`; the configs
@@ -297,6 +301,10 @@ under the root. The watcher starts on first iteration (Python/TypeScript)
 or at the `watch()` call (Rust). The stream never terminates on its own;
 stop consuming it to stop.
 
+Python: each `watch()` call returns an independent stream, and every stream
+on one instance receives every event observed after it was created, so
+several consumers (one per client, say) can share one instance.
+
 Rust: `watch()` may be called once per instance and is mutually exclusive
 with the polling API below — mixing them returns an error, since both drain
 the same underlying filesystem watcher.

dirsql-0.4.84/packages/python/e2e-attestations/bot-1397-watch-broadcast.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/on_file_query_test.py tests/e2e/fanout_test.py tests/e2e/query_contract_test.py tests/integration/binding/async_dirsql_test.py -x -q",
+  "ran_at": 1791309204,
+  "exit_code": 0,
+  "commit": "9a473a8812b974362a7c408132a9724aac50605a",
+  "branch": "bot/1397-watch-broadcast"
+}

dirsql-0.4.84/packages/python/e2e-attestations/claude-1232-config-anchor.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/fanout_test.py tests/e2e/capture_collision_test.py tests/e2e/declared_table_name_test.py tests/e2e/extension_package_test.py tests/e2e/plugin_discovery_test.py tests/e2e/use_case_notebook_test.py tests/e2e/on_file_query_test.py tests/e2e/use_case_transcripts_test.py tests/e2e/plugin_extension_discovery_test.py tests/e2e/use_case_join_test.py tests/e2e/use_case_dossier_test.py tests/e2e/sigint_interrupt_test.py tests/e2e/query_contract_test.py -x -q",
+  "ran_at": 1791304886,
+  "exit_code": 0,
+  "commit": "f34d689dd854cb17c0daad87be0efebb4a45fdb6",
+  "branch": "claude/1232-config-anchor"
+}

dirsql-0.4.84/packages/python/e2e-attestations/claude-1232-multi-watch.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/capture_collision_test.py tests/e2e/declared_table_name_test.py tests/e2e/extension_package_test.py tests/e2e/query_contract_test.py tests/e2e/plugin_discovery_test.py tests/e2e/sigint_interrupt_test.py tests/e2e/fanout_test.py tests/e2e/use_case_transcripts_test.py tests/e2e/plugin_extension_discovery_test.py tests/e2e/on_file_query_test.py -x -q",
+  "ran_at": 1791304050,
+  "exit_code": 0,
+  "commit": "8618c31f0280a80e7d09550fdb931c6460741db7",
+  "branch": "claude/1232-multi-watch"
+}

dirsql-0.4.84/packages/python/e2e-attestations/claude-1232-zero-match.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/fanout_test.py tests/e2e/capture_collision_test.py tests/e2e/declared_table_name_test.py tests/e2e/extension_package_test.py tests/e2e/plugin_discovery_test.py tests/e2e/use_case_notebook_test.py tests/e2e/on_file_query_test.py tests/e2e/use_case_transcripts_test.py tests/e2e/plugin_extension_discovery_test.py tests/e2e/use_case_join_test.py tests/e2e/use_case_dossier_test.py tests/e2e/sigint_interrupt_test.py tests/e2e/query_contract_test.py -x -q",
+  "ran_at": 1791306078,
+  "exit_code": 0,
+  "commit": "8b587de39902adf33e4ebaa957a8fd0005875029",
+  "branch": "claude/1232-zero-match"
+}

dirsql-0.4.84/packages/python/e2e-attestations/claude-1330-python-extensions-patch.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/capture_collision_test.py tests/e2e/fanout_test.py tests/e2e/cli_version_test.py tests/e2e/extension_package_test.py tests/e2e/on_file_query_test.py tests/e2e/sigint_interrupt_test.py tests/e2e/plugin_extension_discovery_test.py tests/e2e/plugin_discovery_test.py tests/e2e/query_contract_test.py -x -q",
+  "ran_at": 1791302302,
+  "exit_code": 0,
+  "commit": "97413988a4b984de31f96d190d2164d61279d7c5",
+  "branch": "claude/1330-python-extensions-patch"
+}

dirsql-0.4.84/packages/python/migrations.d/2026-10-06-config-globs-anchor-at-the-config.md

@@ -0,0 +1,33 @@
+### Config globs anchor at the config file's directory (#1232)
+
+#### Summary
+
+A `[[table]]` `glob` is matched beneath the directory of the config file that wrote it (or, for a `/`, `~/` or `../` glob, beneath its literal prefix), no longer beneath the index root. A config that relied on running from the directory it describes still works when that is also the config's directory; a config kept apart from its data, or one given an explicit root, now indexes the config's directory and needs its globs rewritten.
+
+#### Required changes
+
+| Surface | Before | After |
+| ------- | ------ | ----- |
+| `DirSQL(root="/data", config="/cfg/.dirsql.toml")` with `glob = "**/*.md"` | indexes `/data` | indexes `/cfg`; write `glob = "/data/**/*.md"` to index `/data` |
+| `dirsql -c /cfg/.dirsql.toml` run from `/data` | indexes `/data` | indexes `/cfg` |
+| `ignore` in a config | applied to every table and to path-tables | applies to that config's tables, relative to their anchor |
+| A table over a directory other than the config's | `glob = "docs/*.md"` with the root elsewhere | `glob = "/data/docs/*.md"` or `glob = "~/data/docs/*.md"` |
+| `{root}` in an `on-file` command | the index root | the table's anchor (the config's directory, or the literal prefix of an absolute glob) |
+
+#### Deprecations removed
+
+_None._
+
+#### Behavior changes without code changes
+
+- A config table's `path` column is relative to its anchor.
+- A programmatic table and a path-table still use the index root.
+
+#### Verification
+
+```bash
+mkdir -p /tmp/cfg/projects/p /tmp/elsewhere
+echo '{}' > /tmp/cfg/projects/p/a.jsonl
+printf '[[table]]\nname = "sessions"\nddl = "CREATE TABLE sessions (n TEXT)"\nglob = "projects/*/*.jsonl"\non-file = "echo [{}]"\n' > /tmp/cfg/.dirsql.toml
+cd /tmp/elsewhere && dirsql query "SELECT COUNT(*) AS n FROM sessions" -c /tmp/cfg/.dirsql.toml   # [{"n":1}]
+```

dirsql-0.4.84/packages/python/migrations.d/2026-10-06-watch-broadcast.md

@@ -0,0 +1,46 @@
+### Every Python `watch()` stream receives every event (#1397)
+
+#### Summary
+
+Several `DirSQL.watch()` streams on one Python instance each receive every event, instead of splitting them. A single stream behaves as before. Nothing breaks.
+
+#### Required changes
+
+_None._
+
+#### Deprecations removed
+
+_None._
+
+#### Behavior changes without code changes
+
+- With more than one `watch()` stream on one instance, each stream now yields every event observed after it was created. Code that hand-rolled fan-out over one stream keeps working.
+
+#### Verification
+
+```python
+import asyncio, pathlib, tempfile
+from dirsql import DirSQL, Table
+
+async def main():
+    root = pathlib.Path(tempfile.mkdtemp())
+    table = Table(
+        name="files",
+        ddl="CREATE TABLE files (n INTEGER)",
+        glob="*.json",
+        on_file=lambda path: [{"n": 1}],
+    )
+    db = DirSQL(str(root), tables=[table])
+    await db.ready()
+
+    async def first(stream):
+        async for event in stream:
+            return event.action
+
+    tasks = [asyncio.create_task(first(db.watch())) for _ in range(2)]
+    await asyncio.sleep(0.3)
+    (root / "a.json").write_text("{}")
+    print(await asyncio.wait_for(asyncio.gather(*tasks), 5))  # ['insert', 'insert']
+
+asyncio.run(main())
+```