graphddb 0.1.0 → 0.2.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -1,4 +1,4 @@
1
- import { E as Executor, D as DynamoDBOperation, a as ExecutorResult, B as BatchGetExecInput, P as PutInput, W as WriteExecOptions, b as WriteResult, U as UpdateInput, c as DeleteInput, d as BatchWriteExecItem, T as TransactWriteExecItem, M as ModelStatic, e as DDBModel, C as ChangeEvent } from '../types-CDrWiPxp.js';
1
+ import { E as Executor, D as DynamoDBOperation, a as ExecutorResult, B as BatchGetExecInput, P as PutInput, W as WriteExecOptions, b as WriteResult, U as UpdateInput, c as DeleteInput, d as BatchWriteExecItem, T as TransactWriteExecItem, M as ModelStatic, e as DDBModel, C as ChangeEvent } from '../types-D6qLpw2M.js';
2
2
  import '@aws-sdk/client-dynamodb';
3
3
 
4
4
  /**
@@ -95,7 +95,7 @@ declare class MemoryExecutor implements Executor {
95
95
  * `graphddb/testing` — the in-process test adapter entry point (issue #76).
96
96
  *
97
97
  * `createTestDB()` installs a {@link MemoryExecutor} as GraphDDB's I/O seam, so
98
- * `Model.put/query/list/update/...`, the planner, hydrator and relation
98
+ * `Model.putItem/query/list/updateItem/...`, the planner, hydrator and relation
99
99
  * traversal all run against an in-memory store — **no DynamoDB, no Docker**.
100
100
  * The returned `db.testing` is a {@link MemoryInspector} for asserting the
101
101
  * **physical** layout (PK/SK/GSI as stored, no hydration), seeding fixtures,