storepy 4.4.2__tar.gz → 4.4.4__tar.gz

{storepy-4.4.2/src/storepy.egg-info → storepy-4.4.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: storepy
-Version: 4.4.2
+Version: 4.4.4
 Summary: Multi-backend data layer for Python asyncio (MongoDB, MySQL, SQLite, PostgreSQL, local disk): pure JSON schemas, GQL tree queries compiled to a single native query, GROUP BY/HAVING aggregation, computed columns, soft-delete and role-based access control
 Author-email: leo <coen_ddt@qq.com>
 License-Expression: MIT
@@ -87,6 +87,7 @@ from py_store import init, store
 - [Feedback events](#feedback-events)
 - [Schema reference](#schema-reference)
 - [Transactions](#transaction-boundary)
+- [Triggers](#triggers)
 - [Transactional capabilities](#transactional-capabilities)
 - [FAQ](#faq)
 - [Related projects](#related-projects)
@@ -605,6 +606,30 @@ Computed columns live at the schema top level, `computes: { <key>: { type, fn |
 - Read consistency: only multiple reads inside an explicit session share one transaction connection; reads outside a session do not open an extra transaction.
 - **Cross-source writes (no session)**: a single write call touching ≥2 datasources **cannot be atomic**; it runs sequentially and emits one `non_atomic_write` feedback event (`code: nonAtomic`, with the source list) — degradation is allowed, silence is not. Converge writes onto a single source, or wrap them in `store.session()` (which fails closed on cross-source writes).
 
+## Triggers
+
+Declarative trigger chains on a schema: write events (`insert` / `update` / `remove`) are expanded by the Rust core at plan time into an ordered list of side-effect steps (`plan.triggers`) that the host runs in sequence inside the same atomic envelope as the source write. The declaration form (the `triggers` event keys plus the field table) and the placeholder grammar are defined by the "Triggers" section of the rust-store README; the core's expanded output is byte-for-byte identical across hosts (golden guard: `rust-store/fixtures/triggers/cases.json`).
+
+**Callback wiring** (`py_store/crud/triggers.py`):
+
+```python
+async def _grant_points(args, ctx, host):
+    await host['store'].update('User', {'_id': args['userId']}, {'$inc': {'points': args['amount']}})
+
+store.set_trigger_fn('grantPoints', _grant_points)
+store.assert_trigger_fns_covered(defns)  # startup: a declared fnRef without an implementation ⇒ ERR_TRIGGER_FN_MISSING
+```
+
+**Execution semantics**:
+
+- **Hit test** — an `update` event first checks that the `onFields` values actually changed (a structural deep compare, no-op suppression — an unchanged value does not fire) → then the `when` guard (`eq/ne/gt/gte/lt/lte/in/and/or/not`); `insert` has no `before` and skips the field-level check; `remove` uses the archived (pre-delete) document as root. System fields (`createdAt` / `updatedAt` / `deletedAt`) are excluded from the trigger probe projection, so their changes never fire.
+- **Placeholders** — `{{root.*}}` (post-change value) / `{{before.*}}` (pre-change value) / `{{now}}` undergo whole-value substitution only; embedding a placeholder inside a string raises `ERR_TRIGGER_PLACEHOLDER` — no silent drift.
+- **De-duplication** — within one top-level call, `(step.name, _id)` runs at most once.
+- **Callbacks** — `impl(args, ctx, {'store': store})`; `store.*` inside the callback hits the current transaction connection → the same transaction as the source write.
+- **Scheduled (cron)** — the `schedule` event is enumerated by the host scheduler plugin (`py_store/scheduler/__init__.py`) and reuses the same trigger chain; only `{{now}}` is allowed as a placeholder.
+
+**Boundaries**: single-source real transaction / a cross-source write declares `nonAtomic` / cross-source writes inside `store.session()` fail closed (see [Transaction boundary](#transaction-boundary)); **no cascading** (a trigger write does not fire further triggers); `update_many` does not support field-level triggers (explicitly refused, no silent degradation); the command step `op: "upsert"` is a registration-time `Err`.
+
 ## Transactional capabilities
 
 Capabilities aimed at transactional workloads (orders, inventory — write contention plus

{storepy-4.4.2 → storepy-4.4.4}/README.md

@@ -45,6 +45,7 @@ from py_store import init, store
 - [Feedback events](#feedback-events)
 - [Schema reference](#schema-reference)
 - [Transactions](#transaction-boundary)
+- [Triggers](#triggers)
 - [Transactional capabilities](#transactional-capabilities)
 - [FAQ](#faq)
 - [Related projects](#related-projects)
@@ -563,6 +564,30 @@ Computed columns live at the schema top level, `computes: { <key>: { type, fn |
 - Read consistency: only multiple reads inside an explicit session share one transaction connection; reads outside a session do not open an extra transaction.
 - **Cross-source writes (no session)**: a single write call touching ≥2 datasources **cannot be atomic**; it runs sequentially and emits one `non_atomic_write` feedback event (`code: nonAtomic`, with the source list) — degradation is allowed, silence is not. Converge writes onto a single source, or wrap them in `store.session()` (which fails closed on cross-source writes).
 
+## Triggers
+
+Declarative trigger chains on a schema: write events (`insert` / `update` / `remove`) are expanded by the Rust core at plan time into an ordered list of side-effect steps (`plan.triggers`) that the host runs in sequence inside the same atomic envelope as the source write. The declaration form (the `triggers` event keys plus the field table) and the placeholder grammar are defined by the "Triggers" section of the rust-store README; the core's expanded output is byte-for-byte identical across hosts (golden guard: `rust-store/fixtures/triggers/cases.json`).
+
+**Callback wiring** (`py_store/crud/triggers.py`):
+
+```python
+async def _grant_points(args, ctx, host):
+    await host['store'].update('User', {'_id': args['userId']}, {'$inc': {'points': args['amount']}})
+
+store.set_trigger_fn('grantPoints', _grant_points)
+store.assert_trigger_fns_covered(defns)  # startup: a declared fnRef without an implementation ⇒ ERR_TRIGGER_FN_MISSING
+```
+
+**Execution semantics**:
+
+- **Hit test** — an `update` event first checks that the `onFields` values actually changed (a structural deep compare, no-op suppression — an unchanged value does not fire) → then the `when` guard (`eq/ne/gt/gte/lt/lte/in/and/or/not`); `insert` has no `before` and skips the field-level check; `remove` uses the archived (pre-delete) document as root. System fields (`createdAt` / `updatedAt` / `deletedAt`) are excluded from the trigger probe projection, so their changes never fire.
+- **Placeholders** — `{{root.*}}` (post-change value) / `{{before.*}}` (pre-change value) / `{{now}}` undergo whole-value substitution only; embedding a placeholder inside a string raises `ERR_TRIGGER_PLACEHOLDER` — no silent drift.
+- **De-duplication** — within one top-level call, `(step.name, _id)` runs at most once.
+- **Callbacks** — `impl(args, ctx, {'store': store})`; `store.*` inside the callback hits the current transaction connection → the same transaction as the source write.
+- **Scheduled (cron)** — the `schedule` event is enumerated by the host scheduler plugin (`py_store/scheduler/__init__.py`) and reuses the same trigger chain; only `{{now}}` is allowed as a placeholder.
+
+**Boundaries**: single-source real transaction / a cross-source write declares `nonAtomic` / cross-source writes inside `store.session()` fail closed (see [Transaction boundary](#transaction-boundary)); **no cascading** (a trigger write does not fire further triggers); `update_many` does not support field-level triggers (explicitly refused, no silent degradation); the command step `op: "upsert"` is a registration-time `Err`.
+
 ## Transactional capabilities
 
 Capabilities aimed at transactional workloads (orders, inventory — write contention plus

{storepy-4.4.2 → storepy-4.4.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "storepy"
-version = "4.4.2"
+version = "4.4.4"
 description = "Multi-backend data layer for Python asyncio (MongoDB, MySQL, SQLite, PostgreSQL, local disk): pure JSON schemas, GQL tree queries compiled to a single native query, GROUP BY/HAVING aggregation, computed columns, soft-delete and role-based access control"
 readme = "README.md"
 requires-python = ">=3.10"

{storepy-4.4.2 → storepy-4.4.4}/src/py_store/__init__.py

@@ -350,6 +350,8 @@ class Store:
     run_as_internal = staticmethod(permission.run_as_internal)
     # 自定义权限错误（实例可被 store.PermissionError 捕获）
     PermissionError = permission.PermissionError
+    # 上下文缺失错误（实例可被 store.NoContextError 捕获；fail-secure 下未注入 ctx）
+    NoContextError = permission.NoContextError
     # 原生 SQL 入口错误（实例可被 store.RawSqlError 捕获）
     RawSqlError = datasource.RawSqlError
     # 原生 Mongo 命令入口错误（实例可被 store.NativeCommandError 捕获）

{storepy-4.4.2 → storepy-4.4.4}/src/py_store/crud/exec.py

@@ -19,7 +19,7 @@ from .. import datasource as _datasource
 from ..executors.mongo import exec_mongo as _exec_mongo
 from ..feedback import emit as _emit_feedback
 from ..naming import _to_logical, _to_mongo
-from ..permission import PermissionError, get_context
+from ..permission import NoContextError, PermissionError, get_context
 from ..schema import get as _schema_get
 
 _PHASE1_IDS = re.compile(r'^\{\{phase1\.ids\}\}$')
@@ -35,6 +35,11 @@ _PERM_PREFIX = 'ERR_PERMISSION:'
 # 反馈事件 `profile_blocked`（自动反馈原则：允许拦截，禁止静默）。
 _PROFILE_PREFIX = 'ERR_TEXT2QUERY:'
 
+# 上下文缺失识别：core fail-secure（require_context / secure_mode）下无 ctx 时统一携带
+# `ERR_NO_CONTEXT:` 稳定前缀（见 core `command/mod.rs`），同上按前缀映射。命中即抛
+# `NoContextError`（与 PermissionError 同档 403；前缀剥离）。
+_NO_CONTEXT_PREFIX = 'ERR_NO_CONTEXT:'
+
 # 从 core 文案 `... [$feature]（功能收缩）` 中提取门禁项名；无 `[..]` 时留白（None），
 # 不伪造 feature —— 缺值必须显式暴露（禁静默兜底）。
 _FEATURE_RE = re.compile(r'\[(.+?)\]')
@@ -85,6 +90,7 @@ def _call(fn):
     """绑定层调用包装：
 
       - 权限类错误（``ERR_PERMISSION:`` 前缀）→ ``PermissionError``
+      - 上下文缺失（``ERR_NO_CONTEXT:`` 前缀）→ ``NoContextError``（同档 403）
       - 档位类错误（``ERR_TEXT2QUERY:`` 前缀）→ emit ``profile_blocked`` 反馈 + ``ProfileViolation``
 
     按前缀映射而非具体文案（core 文案可自由调整，映射不随文案漂移而静默失效）。
@@ -96,6 +102,8 @@ def _call(fn):
         msg = str(e)
         if msg.startswith(_PERM_PREFIX):
             raise PermissionError(msg[len(_PERM_PREFIX):]) from e
+        if msg.startswith(_NO_CONTEXT_PREFIX):
+            raise NoContextError(msg[len(_NO_CONTEXT_PREFIX):]) from e
         if msg.startswith(_PROFILE_PREFIX):
             detail = msg[len(_PROFILE_PREFIX):]
             m = _FEATURE_RE.search(detail)

{storepy-4.4.2 → storepy-4.4.4}/src/py_store/permission.py

@@ -184,3 +184,18 @@ class PermissionError(Exception):
     def __init__(self, message, status=403):
         super().__init__(message)
         self.status = status
+
+
+class NoContextError(Exception):
+    """上下文缺失错误（fail-secure：require_context 开启 / secure_mode 下未注入 ctx）
+
+    与 PermissionError 同属权限上下文类（403）：core 抛 ``ERR_NO_CONTEXT:`` 稳定前缀
+    （见 core ``command/mod.rs``），由 ``crud.exec._call`` 归一为本类型（前缀已剥离）。
+    ``code`` 与 core machine code 对齐（``no_context``），供皮按枚举判定（禁按文案匹配）。
+    对齐 nodejs-store ``NoContextError``。
+    """
+
+    def __init__(self, message, status=403):
+        super().__init__(message)
+        self.code = 'no_context'
+        self.status = status

{storepy-4.4.2 → storepy-4.4.4/src/storepy.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: storepy
-Version: 4.4.2
+Version: 4.4.4
 Summary: Multi-backend data layer for Python asyncio (MongoDB, MySQL, SQLite, PostgreSQL, local disk): pure JSON schemas, GQL tree queries compiled to a single native query, GROUP BY/HAVING aggregation, computed columns, soft-delete and role-based access control
 Author-email: leo <coen_ddt@qq.com>
 License-Expression: MIT
@@ -87,6 +87,7 @@ from py_store import init, store
 - [Feedback events](#feedback-events)
 - [Schema reference](#schema-reference)
 - [Transactions](#transaction-boundary)
+- [Triggers](#triggers)
 - [Transactional capabilities](#transactional-capabilities)
 - [FAQ](#faq)
 - [Related projects](#related-projects)
@@ -605,6 +606,30 @@ Computed columns live at the schema top level, `computes: { <key>: { type, fn |
 - Read consistency: only multiple reads inside an explicit session share one transaction connection; reads outside a session do not open an extra transaction.
 - **Cross-source writes (no session)**: a single write call touching ≥2 datasources **cannot be atomic**; it runs sequentially and emits one `non_atomic_write` feedback event (`code: nonAtomic`, with the source list) — degradation is allowed, silence is not. Converge writes onto a single source, or wrap them in `store.session()` (which fails closed on cross-source writes).
 
+## Triggers
+
+Declarative trigger chains on a schema: write events (`insert` / `update` / `remove`) are expanded by the Rust core at plan time into an ordered list of side-effect steps (`plan.triggers`) that the host runs in sequence inside the same atomic envelope as the source write. The declaration form (the `triggers` event keys plus the field table) and the placeholder grammar are defined by the "Triggers" section of the rust-store README; the core's expanded output is byte-for-byte identical across hosts (golden guard: `rust-store/fixtures/triggers/cases.json`).
+
+**Callback wiring** (`py_store/crud/triggers.py`):
+
+```python
+async def _grant_points(args, ctx, host):
+    await host['store'].update('User', {'_id': args['userId']}, {'$inc': {'points': args['amount']}})
+
+store.set_trigger_fn('grantPoints', _grant_points)
+store.assert_trigger_fns_covered(defns)  # startup: a declared fnRef without an implementation ⇒ ERR_TRIGGER_FN_MISSING
+```
+
+**Execution semantics**:
+
+- **Hit test** — an `update` event first checks that the `onFields` values actually changed (a structural deep compare, no-op suppression — an unchanged value does not fire) → then the `when` guard (`eq/ne/gt/gte/lt/lte/in/and/or/not`); `insert` has no `before` and skips the field-level check; `remove` uses the archived (pre-delete) document as root. System fields (`createdAt` / `updatedAt` / `deletedAt`) are excluded from the trigger probe projection, so their changes never fire.
+- **Placeholders** — `{{root.*}}` (post-change value) / `{{before.*}}` (pre-change value) / `{{now}}` undergo whole-value substitution only; embedding a placeholder inside a string raises `ERR_TRIGGER_PLACEHOLDER` — no silent drift.
+- **De-duplication** — within one top-level call, `(step.name, _id)` runs at most once.
+- **Callbacks** — `impl(args, ctx, {'store': store})`; `store.*` inside the callback hits the current transaction connection → the same transaction as the source write.
+- **Scheduled (cron)** — the `schedule` event is enumerated by the host scheduler plugin (`py_store/scheduler/__init__.py`) and reuses the same trigger chain; only `{{now}}` is allowed as a placeholder.
+
+**Boundaries**: single-source real transaction / a cross-source write declares `nonAtomic` / cross-source writes inside `store.session()` fail closed (see [Transaction boundary](#transaction-boundary)); **no cascading** (a trigger write does not fire further triggers); `update_many` does not support field-level triggers (explicitly refused, no silent degradation); the command step `op: "upsert"` is a registration-time `Err`.
+
 ## Transactional capabilities
 
 Capabilities aimed at transactional workloads (orders, inventory — write contention plus

{storepy-4.4.2 → storepy-4.4.4}/tests/test_require_context.py

@@ -123,13 +123,13 @@ def test_require_context_on_blocks_without_ctx():
     _mock([{'_id': '1', 'title': 'a'}])
     _sc.set_require_context(True)
     try:
-        with pytest.raises(RuntimeError, match='ERR_NO_CONTEXT'):
+        with pytest.raises(perm.NoContextError):
             _run(_crud_mod.query('RcModel{title}'))
-        with pytest.raises(RuntimeError, match='ERR_NO_CONTEXT'):
+        with pytest.raises(perm.NoContextError):
             _run(_crud_mod.insert('RcModel', {'title': 'x'}))
-        with pytest.raises(RuntimeError, match='ERR_NO_CONTEXT'):
+        with pytest.raises(perm.NoContextError):
             _run(_crud_mod.update('RcModel', {'_id': '1'}, {'title': 'y'}))
-        with pytest.raises(RuntimeError, match='ERR_NO_CONTEXT'):
+        with pytest.raises(perm.NoContextError):
             _run(_crud_mod.remove('RcModel', {'_id': '1'}))
     finally:
         _sc.set_require_context(False)
@@ -177,9 +177,9 @@ def test_secure_mode_flips_switches_blocks_ctxless():
         assert secure.is_secure() is True
         assert _sc.require_context() is True
         # 开关1 require_context：无 ctx 读写拒绝
-        with pytest.raises(RuntimeError, match='ERR_NO_CONTEXT'):
+        with pytest.raises(perm.NoContextError):
             _run(_crud_mod.query('RcModel{title}'))
-        with pytest.raises(RuntimeError, match='ERR_NO_CONTEXT'):
+        with pytest.raises(perm.NoContextError):
             _run(_crud_mod.insert('RcModel', {'title': 'x'}))
         # 开关3 meta closed：无 ctx 注册新定义拒绝
         with pytest.raises(RuntimeError, match='ERR_PERMISSION'):