dirsql 0.4.119__tar.gz → 0.4.121__tar.gz

{dirsql-0.4.119 → dirsql-0.4.121}/Cargo.lock

@@ -573,7 +573,7 @@ dependencies = [
 
 [[package]]
 name = "dirsql"
-version = "0.4.119"
+version = "0.4.121"
 dependencies = [
  "assert_cmd",
  "axum",
@@ -625,7 +625,7 @@ dependencies = [
 
 [[package]]
 name = "dirsql-py-ext"
-version = "0.4.119"
+version = "0.4.121"
 dependencies = [
  "dirsql",
  "pyo3",

{dirsql-0.4.119 → dirsql-0.4.121}/PKG-INFO

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

{dirsql-0.4.119/packages/rust → dirsql-0.4.121}/docs/reference/config.md

@@ -374,9 +374,12 @@ foreign key violation: `task` row from `projects/beta/tasks/t1.json` has project
   batch that touches the same table carries the orphaning change and waits
   too.
 
-`ON DELETE` and `ON UPDATE` actions are not deferred. `dirsql` applies a changed
-file as a delete and an insert, so `ON DELETE CASCADE` deletes the children of a
-parent whose file is edited or renamed, even though their files still exist.
+`ON DELETE` and `ON UPDATE` actions are not deferred. A parent table with a
+`PRIMARY KEY`, or a `UNIQUE` column its rows fill, has an edited row `UPDATE`d
+in place, so its children stay. A table without one has a changed row deleted
+and inserted, so `ON DELETE CASCADE` deletes the children of a parent whose
+file is edited. A row whose key changes, as when the key is taken from a
+renamed file's name, is a delete and an insert either way.
 
 ### `on-file` row mapping
 

{dirsql-0.4.119 → dirsql-0.4.121}/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.119"
+version = "0.4.121"
 # 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.121/packages/python/changelog.d/2026-11-02-watch-dirs-created-mid-registration.md

@@ -0,0 +1 @@
+**Fixed** On Linux, a directory created inside a new directory before the watcher registered that new directory is now watched too. Before, files written into it later produced no events.

{dirsql-0.4.119 → dirsql-0.4.121/packages/python}/docs/reference/config.md

@@ -374,9 +374,12 @@ foreign key violation: `task` row from `projects/beta/tasks/t1.json` has project
   batch that touches the same table carries the orphaning change and waits
   too.
 
-`ON DELETE` and `ON UPDATE` actions are not deferred. `dirsql` applies a changed
-file as a delete and an insert, so `ON DELETE CASCADE` deletes the children of a
-parent whose file is edited or renamed, even though their files still exist.
+`ON DELETE` and `ON UPDATE` actions are not deferred. A parent table with a
+`PRIMARY KEY`, or a `UNIQUE` column its rows fill, has an edited row `UPDATE`d
+in place, so its children stay. A table without one has a changed row deleted
+and inserted, so `ON DELETE CASCADE` deletes the children of a parent whose
+file is edited. A row whose key changes, as when the key is taken from a
+renamed file's name, is a delete and an insert either way.
 
 ### `on-file` row mapping
 

dirsql-0.4.121/packages/python/e2e-attestations/bot-1461-step3-1020.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/glob_speed_one_level_test.py tests/e2e/glob_speed_recursive_test.py tests/e2e/glob_speed_dotfiles_test.py tests/e2e/glob_speed_gitignore_test.py tests/e2e/glob_speed_node_modules_test.py tests/e2e/query_contract_test.py -x -q",
+  "ran_at": 1792499219,
+  "exit_code": 0,
+  "commit": "f0b743744d6e038ad678de855df59c843e109ad1",
+  "branch": "bot/1461-step3-1020"
+}

dirsql-0.4.121/packages/python/e2e-attestations/bot-1478-perdir-walk-1020.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/glob_speed_depth_bound_test.py tests/e2e/glob_speed_one_level_test.py tests/e2e/glob_speed_recursive_test.py tests/e2e/glob_speed_matchers_test.py tests/e2e/glob_speed_dotfiles_test.py tests/e2e/glob_speed_gitignore_test.py tests/e2e/glob_speed_node_modules_test.py tests/e2e/glob_speed_symlink_test.py tests/e2e/query_contract_test.py tests/e2e/fanout_test.py tests/e2e/use_case_join_test.py tests/e2e/stat_speed_test.py tests/e2e/release_speed_test.py -q",
+  "ran_at": 1792499019,
+  "exit_code": 0,
+  "commit": "9647c7ae1dab28acb9c211eced8f82624376b3b2",
+  "branch": "bot/1478-perdir-walk-1020"
+}

dirsql-0.4.121/packages/python/e2e-attestations/bot-1544-perfile-update-1020.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run --no-sync python -m pytest tests/e2e/watch_speed_test.py tests/e2e/on_file_query_test.py tests/e2e/fanout_test.py -q -p no:cacheprovider",
+  "ran_at": 1792496178,
+  "exit_code": 0,
+  "commit": "f4fd6d6b79a97b877a175884e377004b7ff144f2",
+  "branch": "bot/1544-perfile-update-1020"
+}

dirsql-0.4.121/packages/python/e2e-attestations/bot-1557-watch-rename-1102.json

@@ -0,0 +1,7 @@
+{
+  "command": "uv run python -m pytest tests/e2e/watch_speed_test.py tests/e2e/jsonl_parse_speed_test.py tests/e2e/on_file_query_test.py tests/e2e/fanout_test.py -q",
+  "ran_at": 1793653639,
+  "exit_code": 0,
+  "commit": "90967ba7a324453df04aa604126a0d4c004ea887",
+  "branch": "bot/1557-watch-rename-1102"
+}

dirsql-0.4.121/packages/python/migrations.d/2026-11-02-watch-dirs-created-mid-registration.md

@@ -0,0 +1,29 @@
+### Directories created mid-registration are watched
+
+#### Summary
+
+On Linux, the watcher walks a new directory again after watching it, until a walk finds nothing new, so a subdirectory created in between is watched too. Nothing breaks.
+
+#### Required changes
+
+_None._
+
+#### Deprecations removed
+
+_None._
+
+#### Behavior changes without code changes
+
+Files written into a directory created in a burst of nested `mkdir`s now produce events where some were missed before.
+
+#### Verification
+
+```bash
+dirsql init
+dirsql server -c .dirsql.toml &
+curl -sN http://localhost:7117/events &
+mkdir -p a/b/c/d/e/f/g
+echo '{"id":"1","name":"x"}' > a/b/c/d/e/f/g/r.json
+```
+
+Prints an insert for `a/b/c/d/e/f/g/r.json`.

{dirsql-0.4.119 → dirsql-0.4.121}/packages/rust/Cargo.toml

@@ -6,7 +6,7 @@ description = "Ephemeral SQL index over a local directory"
 # version stays for the binding crates (publish = false). The literal
 # intentionally lags the published version: putitoutthere rewrites it to
 # the planned release version at build time and never commits it back.
-version = "0.4.119"
+version = "0.4.121"
 edition.workspace = true
 # Literal `license` (not `license.workspace = true`) because
 # putitoutthere's preflight check reads `[package].license` directly

{dirsql-0.4.119/packages/python → dirsql-0.4.121/packages/rust}/docs/reference/config.md

@@ -374,9 +374,12 @@ foreign key violation: `task` row from `projects/beta/tasks/t1.json` has project
   batch that touches the same table carries the orphaning change and waits
   too.
 
-`ON DELETE` and `ON UPDATE` actions are not deferred. `dirsql` applies a changed
-file as a delete and an insert, so `ON DELETE CASCADE` deletes the children of a
-parent whose file is edited or renamed, even though their files still exist.
+`ON DELETE` and `ON UPDATE` actions are not deferred. A parent table with a
+`PRIMARY KEY`, or a `UNIQUE` column its rows fill, has an edited row `UPDATE`d
+in place, so its children stay. A table without one has a changed row deleted
+and inserted, so `ON DELETE CASCADE` deletes the children of a parent whose
+file is edited. A row whose key changes, as when the key is taken from a
+renamed file's name, is a delete and an insert either way.
 
 ### `on-file` row mapping