graphddb-runtime 1.0.1__tar.gz → 1.0.2__tar.gz

{graphddb_runtime-1.0.1 → graphddb_runtime-1.0.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: graphddb-runtime
-Version: 1.0.1
+Version: 1.0.2
 Summary: Thin DynamoDB executor for GraphDDB-generated Python repositories (single-operation core, issue #44).
 License: MIT
 Requires-Python: >=3.9

{graphddb_runtime-1.0.1 → graphddb_runtime-1.0.2}/graphddb_runtime/runtime.py

@@ -2327,6 +2327,31 @@ class GraphDDBRuntime:
                 command_id, spec, params, names, values, sets
             )
 
+            # #333: an UpdateItem that CREATES a row (create-if-absent) must carry the
+            # model's key-source field attributes, like PutItem does. SET each field a
+            # `keyCondition` template references from the command's key params. A
+            # key-source field is immutable for a given key, so a plain SET to the
+            # key-derived value is a safe no-op on existing rows and populates it on
+            # create. Without this, a row first created by an update lacks e.g. `child`,
+            # so a projection of that field returns empty. (Skipped when add_only — the
+            # #301 fallback only fires on rows that already exist.)
+            seen_ks: set = set()
+            for tmpl in spec["keyCondition"].values():
+                for m in _PLACEHOLDER_RE.finditer(str(tmpl)):
+                    field = m.group(0)[1:-1]
+                    if "." in field or field in seen_ks or field not in params:
+                        continue
+                    raw = params[field]
+                    if raw is None:
+                        continue
+                    seen_ks.add(field)
+                    idx = len(seen_ks) - 1
+                    n = f"#ks{idx}"
+                    v = f":ks{idx}"
+                    names[n] = field
+                    values[v] = self._serializer.serialize(raw)
+                    sets.append(f"{n} = {v}")
+
         # #301: atomic-`ADD` clauses (`ADD #a :d`, a caller `param.number()` delta).
         # Built AFTER the SET so an ADD-only expression (`add_only`, or an update
         # whose SET change set is empty) is legal — DynamoDB's `SET … ADD …` is one

{graphddb_runtime-1.0.1 → graphddb_runtime-1.0.2}/graphddb_runtime.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: graphddb-runtime
-Version: 1.0.1
+Version: 1.0.2
 Summary: Thin DynamoDB executor for GraphDDB-generated Python repositories (single-operation core, issue #44).
 License: MIT
 Requires-Python: >=3.9

{graphddb_runtime-1.0.1 → graphddb_runtime-1.0.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "graphddb-runtime"
-version = "1.0.1"
+version = "1.0.2"
 description = "Thin DynamoDB executor for GraphDDB-generated Python repositories (single-operation core, issue #44)."
 readme = "README.md"
 requires-python = ">=3.9"

{graphddb_runtime-1.0.1 → graphddb_runtime-1.0.2}/tests/test_atomic_add_command.py

@@ -168,6 +168,22 @@ def test_mark_fallback_add_only_on_condition_fail():
     assert any(v == {"N": "1"} for v in fvals.values()), fvals
 
 
+def test_mark_stores_key_source_fields():
+    """#333: an UpdateItem that CREATES the row must persist the key-source field
+    attributes (part/child) via a plain SET — like PutItem — so a row first created
+    by the mark carries them and a projection of e.g. ``child`` is not empty."""
+    client = _MarkClient(fail_first=False)
+    rt = _mark_runtime(client)
+
+    rt.execute_command("StatsTreeCmd__mark", _MARK_PARAMS)
+
+    req = client.updates[0]
+    assert _has_set_clause(req["UpdateExpression"]), req["UpdateExpression"]
+    names = set(req["ExpressionAttributeNames"].values())
+    for field in ("part", "child"):
+        assert field in names, f"key-source field {field!r} must be SET (#333); {names}"
+
+
 def test_mark_non_ccf_error_propagates():
     """A NON-condition error on the primary must NOT be swallowed by the two-stage —
     it propagates and no ADD-only fallback fires. Parity with the Rust

{graphddb_runtime-1.0.1 → graphddb_runtime-1.0.2}/tests/test_unit.py

@@ -253,9 +253,12 @@ def test_update_item_builds_set_expression():
     method, req = client.calls[0]
     assert method == "update_item"
     assert plain(req["Key"]) == {"PK": "USER#alice", "SK": "PROFILE"}
-    assert req["UpdateExpression"] == "SET #c0 = :c0"
-    assert req["ExpressionAttributeNames"] == {"#c0": "status"}
-    assert plain(req["ExpressionAttributeValues"]) == {":c0": "disabled"}
+    # #333: the update also SETs the key-source field(s) the PK/SK templates
+    # reference (here `userId`, from `USER#{userId}`) so a row first created by this
+    # update carries them like a PutItem would — a no-op on an existing row.
+    assert req["UpdateExpression"] == "SET #c0 = :c0, #ks0 = :ks0"
+    assert req["ExpressionAttributeNames"] == {"#c0": "status", "#ks0": "userId"}
+    assert plain(req["ExpressionAttributeValues"]) == {":c0": "disabled", ":ks0": "alice"}
 
 
 def test_update_item_rederives_affected_gsi_key():
@@ -303,7 +306,8 @@ def test_update_item_does_not_touch_unaffected_gsi():
     rt.execute_command("UserConfCommands__disableUser", {"userId": "alice", "status": "disabled"})
     _method, req = client.calls[0]
     assert "GSI1PK" not in req["ExpressionAttributeNames"].values()
-    assert req["UpdateExpression"] == "SET #c0 = :c0"
+    # #333: the change SET plus the key-source SET (`userId`); no GSI re-derive.
+    assert req["UpdateExpression"] == "SET #c0 = :c0, #ks0 = :ks0"
 
 
 def test_put_item_injects_key_attributes():