dirsql 0.4.115 → 0.4.116

package/docs/howto/react-to-changes.md

@@ -7,7 +7,8 @@ side.
 
 Row events are emitted for **named tables**, so this flow needs a config —
 [path-tables](../reference/path-tables.md) are scanned per query and are not
-watched. Define one next to your files. A named table's columns are whatever
+watched, so `watch()` on an instance with no named tables raises an error and
+`/events` returns `503`. Define one next to your files. A named table's columns are whatever
 its [`on-file`](../reference/config.md#table) hook emits; here a minimal hook
 prints each file's basename:
 

package/docs/reference/http-api.md

@@ -115,4 +115,4 @@ Row values serialize as in [`POST /query`](#value-serialization).
 |---|---|
 | `200` | Stream opened (`text/event-stream`). |
 | `405` | `POST /events`. Plain-text body `method not allowed`. |
-| `503` | The server is in [degraded mode](./cli.md#degraded-mode), or its filesystem watcher failed to start (for example, the inotify limit is exhausted). JSON `{"error": …}` body; for a watcher failure the message starts `filesystem watcher failed to start:` and gives the reason. `POST /query` keeps working. |
+| `503` | The server is in [degraded mode](./cli.md#degraded-mode), or its filesystem watcher failed to start (for example, the inotify limit is exhausted, or the instance has no named tables). JSON `{"error": …}` body; for a watcher failure the message starts `filesystem watcher failed to start:` and gives the reason. `POST /query` keeps working. |

package/docs/reference/sdk.md

@@ -301,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.
 
+An instance with no named tables cannot be watched: path-tables emit no
+watch events, so `watch()` (and the polling primitives) raise an error naming
+that cause. Define a table first.
+
 Python/TypeScript: 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.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "dirsql",
-  "version": "0.4.115",
+  "version": "0.4.116",
   "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.115",
-    "@dirsql/lib-linux-arm64-gnu": "0.4.115",
-    "@dirsql/lib-darwin-x64": "0.4.115",
-    "@dirsql/lib-darwin-arm64": "0.4.115",
-    "@dirsql/lib-win32-x64-msvc": "0.4.115"
+    "@dirsql/lib-linux-x64-gnu": "0.4.116",
+    "@dirsql/lib-linux-arm64-gnu": "0.4.116",
+    "@dirsql/lib-darwin-x64": "0.4.116",
+    "@dirsql/lib-darwin-arm64": "0.4.116",
+    "@dirsql/lib-win32-x64-msvc": "0.4.116"
   }
 }