xync-db 0.2.1__tar.gz → 0.3.0__tar.gz

{xync_db-0.2.1 → xync_db-0.3.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: xync-db
-Version: 0.2.1
+Version: 0.3.0
 Summary: Xync DB schema: Tortoise ORM models, enums, pydantic DTOs.
 Author-email: Mike Artemiev <mixartemev@gmail.com>
 License: LicenseRef-EULA

xync_db-0.3.0/src/xync_db/migrations/models/0005_credex_del.py

@@ -0,0 +1,42 @@
+"""Per-CredEx delete trigger → `credexs_del` channel.
+
+Lets a user unregister ONE credential from ONE exchange (settings/creds edit form): deleting a
+single `credex` row reactively removes it from that exchange (mirror of `credexs_new`, which posts
+a freshly inserted `CredEx(exid=0)`). The handler is `api.handlers.creds.credex_del`.
+
+The default `plsql("credex")` DEL trigger (from 0002) only carried `OLD.id`, useless post-cascade.
+We override it: emit `[person_id, ex_id, exid]` (person via the still-living parent `cred`) — exactly
+what the handler needs to find the agent and call `acl.cred_del(exid)`.
+
+Crucially we SKIP the notify when the parent `cred` is already gone: that's a `Cred` cascade-delete,
+where the BEFORE-DELETE `cred_del()` trigger already snapshotted every credex into `creds_del`. Firing
+here too would double-delete on the exchange. A standalone credex delete leaves the cred alive → notify.
+"""
+
+from typing import ClassVar
+
+from tortoise.migrations.migration import Migration as BaseMigration
+from tortoise.migrations.operations import RunSQL
+
+CREDEX_DEL_SQL = """
+CREATE OR REPLACE FUNCTION credex_del() returns trigger as $credex_del_trg$
+DECLARE
+    pid INT;
+BEGIN
+    -- person via the parent cred; NULL ⇒ cred already cascade-deleted ⇒ cred_del() handled it ⇒ skip
+    SELECT person_id INTO pid FROM cred WHERE id = OLD.cred_id;
+    IF pid IS NOT NULL THEN
+        PERFORM pg_notify('credexs_del', jsonb_build_array(pid, OLD.ex_id, OLD.exid)::varchar);
+    END IF;
+    RETURN NULL;
+END
+$credex_del_trg$ LANGUAGE plpgsql;
+CREATE OR REPLACE TRIGGER credex_del AFTER DELETE ON "credex" FOR EACH ROW EXECUTE FUNCTION credex_del();
+
+
+"""
+
+
+class Migration(BaseMigration):
+    dependencies: ClassVar = [("models", "0004_all_seed")]
+    operations: ClassVar = [RunSQL(CREDEX_DEL_SQL)]

xync_db-0.3.0/src/xync_db/migrations/models/0006_credex_orphan.py

@@ -0,0 +1,47 @@
+"""Per-CredEx exid-overwrite trigger → `credexs_orphan` channel.
+
+`CredEx.upsert` keys on (cred, ex) and overwrites `exid`. When it overwrites a REAL (non-zero) exid
+with a different value, the previously-registered credential keeps living on the exchange as an
+orphaned duplicate (the DB no longer tracks it). We don't silently leak it: a BEFORE-UPDATE trigger
+catches the change and emits `[person_id, ex_id, OLD.exid, OLD.cred_id]` so service-api can ask the
+owner whether to delete the stale one (handler `api.handlers.creds.credex_orphan`, mirror of the
+`is_you` consent flow). On "yes" the answer routes back through `CredEx.orphan_del` →
+`credexs_orphan_del` → `credex_orphan_del` handler → `acl.cred_del(OLD.exid)` + a success/error report.
+
+`OLD.cred_id` is in the payload because the orphan-consent question shows the credential's `detail`,
+which the handler can't recover from `[person_id, ex_id, OLD.exid]` alone: post-overwrite the (cred,
+ex) row already holds the NEW exid, and a person may own several creds on one exchange.
+
+Fires ONLY on a genuine real→different overwrite:
+  - `OLD.exid <> 0` skips the normal publish (stub 0 → real exid in `credex_new`);
+  - `NEW.exid <> OLD.exid` skips no-op re-writes (parse re-saving the same exid).
+The user re-registers immediately (the overwrite proceeds — `RETURN NEW`); orphan cleanup is async
+and consent-gated. person via the parent cred; NULL ⇒ no owner to ask ⇒ skip.
+"""
+
+from typing import ClassVar
+
+from tortoise.migrations.migration import Migration as BaseMigration
+from tortoise.migrations.operations import RunSQL
+
+CREDEX_ORPHAN_SQL = """
+CREATE OR REPLACE FUNCTION credex_orphan() returns trigger as $credex_orphan_trg$
+DECLARE
+    pid INT;
+BEGIN
+    IF OLD.exid <> 0 AND NEW.exid <> OLD.exid THEN
+        SELECT person_id INTO pid FROM cred WHERE id = OLD.cred_id;
+        IF pid IS NOT NULL THEN
+            PERFORM pg_notify('credexs_orphan', jsonb_build_array(pid, OLD.ex_id, OLD.exid, OLD.cred_id)::varchar);
+        END IF;
+    END IF;
+    RETURN NEW;
+END
+$credex_orphan_trg$ LANGUAGE plpgsql;
+CREATE OR REPLACE TRIGGER credex_orphan BEFORE UPDATE ON "credex" FOR EACH ROW EXECUTE FUNCTION credex_orphan();
+"""
+
+
+class Migration(BaseMigration):
+    dependencies: ClassVar = [("models", "0005_credex_del")]
+    operations: ClassVar = [RunSQL(CREDEX_ORPHAN_SQL)]

{xync_db-0.2.1 → xync_db-0.3.0}/src/xync_db/models/__init__.py

@@ -1588,6 +1588,29 @@ class CredEx(Model):
         credex, _ = await cls.update_or_create({"exid": exid}, cred_id=cred_id, ex_id=ex_id)
         return credex
 
+    @classmethod
+    async def remove(cls, *, cred_id: int, ex_id: int) -> bool:
+        """ЕДИНСТВЕННЫЙ standalone-делитор CredEx (single-writer-правило): сносит строку (cred, ex).
+        Снятие креда с ОДНОЙ биржи из формы — удаление на бирже реактивно: BEFORE/AFTER-DELETE триггер
+        `credex_del` (миграция 0005) положит `[person_id, ex_id, exid]` в `credexs_del` → handler вызовет
+        `acl.cred_del(exid)`. Каскадное удаление при сносе самого Cred идёт другим путём (`creds_del`)."""
+        return bool(await cls.filter(cred_id=cred_id, ex_id=ex_id).delete())
+
+    @classmethod
+    async def orphan_del(cls, *, person_id: int, ex_id: int, exid: int) -> None:
+        """Удалить ОСИРОТЕВШИЙ exid на бирже — после согласия владельца (web-контроллер / бот-колбэк).
+        Перезапись exid у строки (cred, ex) на другой оставляет старый реквизит висеть на бирже дубликатом;
+        BEFORE-UPDATE триггер `credex_orphan` (миграция 0006) ловит это и шлёт `credexs_orphan` → handler
+        спрашивает владельца. На «да» зовут СЮДА: свой канал `credexs_orphan_del` (НЕ переиспользуем
+        `credexs_del`) — его handler `credex_orphan_del` делает `acl.cred_del(exid)` по (person, ex) И
+        возвращает владельцу результат (успех/ошибка) тем же Notify; у обычного `credex_del` отчёта нет,
+        поэтому каналы разделены. Строки CredEx для старого exid уже нет, и она не нужна. Единый эмиттер,
+        чтобы канал/полезную нагрузку не дублировать в web- и bot-зонах."""
+        await connections.get("default").execute_query(
+            "SELECT pg_notify('credexs_orphan_del', jsonb_build_array($1::int, $2::int, $3::bigint)::varchar)",
+            [person_id, ex_id, exid],
+        )
+
     class Meta:
         table_description = "Credential on Exchange"
         unique_together = (("ex", "exid"),)