@procedures/mongo 0.15.0 → 0.16.0

package/CHANGELOG.md

@@ -1,5 +1,27 @@
 # @procedures/mongo
 
+## 0.16.0
+
+### Patch Changes
+
+- Updated dependencies [deada4b]
+  - @procedures/client@0.16.0
+  - @procedures/collections@0.16.0
+
+## 0.15.1
+
+### Patch Changes
+
+- bce8f5c: New: `MongoViewStorage`, a read-only storage of one materialized view for the collection procedures (roadmap CLI-38). A `ViewMaterializer` writes a big rebuild as a new generation in groups, and then it changes the generation in the status of the view. During the rebuild, a plain query of the target reads the rows of two generations.
+  
+  Each read of `MongoViewStorage` finds the current generation of the view one time, and reads only its rows (`viewFilter`). Thus `get`, `getAll`, `find`, `changes` and the other reads of the procedures give one whole generation. The key of a row is its text `_id` in the result of the pipeline. Each write rejects with `FORBIDDEN`, because only the materializer writes a target. Collections that are not views keep their storages, and nothing changes for them.
+- Updated dependencies [c78da2d]
+- Updated dependencies [d99b2d5]
+- Updated dependencies [534e4ea]
+- Updated dependencies [44fdd60]
+  - @procedures/client@0.15.1
+  - @procedures/collections@0.15.1
+
 ## 0.15.0
 
 ### Minor Changes

package/README.md

@@ -742,6 +742,14 @@ const totals = await db.collection("orderTotals").find(viewFilter(view)).toArray
 - A pass keeps in memory the key of each row of the result (at most `maxRows`) and one group of rows. It keeps nothing between passes.
 - An app with targets from an older materializer (the plain key as `_id`, no generation) needs no migration step. The first pass of each view writes its rows in a generation, and removes the rows of its partition with no generation. A row without the partition field stays.
 
+To serve a view through the collection procedures, give its storage `new MongoViewStorage({ view: "totals", db })` (roadmap CLI-38):
+
+- Each read finds the current generation of the view one time, and reads only its rows. A reader of `get`, `getAll`, `find` or `changes` thus gets one generation only.
+- A read that starts before a change of generation ends on the previous generation. The materializer keeps its rows for `generationGrace`, so a read must end in that time.
+- The key of a row is its `_id` in the result, a text. The value has that `_id` and the fields of the row.
+- The storage is read-only: a write rejects with `FORBIDDEN`. It has no change log.
+- Give it the same `views`, `partitionField`, `statusField` and `targetId` as the materializer.
+
 ## Integration with Ecosystem
 
 ### Bundle Packages