@procedures/mongo 0.48.1 → 0.48.2
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.
- package/CHANGELOG.md +12 -0
- package/dist/.tsbuildinfo +1 -1
- package/dist/storage/document-storage.d.ts +6 -0
- package/dist/storage/document-storage.d.ts.map +1 -1
- package/dist/storage/document-storage.js +63 -22
- package/dist/storage/document-storage.js.map +1 -1
- package/package.json +4 -4
- package/src/storage/document-storage.ts +59 -22
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,17 @@
|
|
|
1
1
|
# @procedures/mongo
|
|
2
2
|
|
|
3
|
+
## 0.48.2
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- aa4ce41: `MongoDocumentStorage`: a plain write of a new id does not fail when another process writes that id at the same time. Before this fix, `set`, `setBatch` or `patch` could reject with a duplicate key, and the store kept the value of the other process. A batch also did not make the writes after the stopped write. The write tries again with the same number, so a reader does not pass it. A write with a guard keeps its conflict error. A real duplicate reaches the caller after one more try.
|
|
8
|
+
- 08beec5: A write that a write in flight holds back reaches its subscribers with no later write. `StorageChanges` has a new optional field `held`. The docs state that a result gives each write at least one time. They name the two cases of a second time. A read of the log with no change does not move the `since` of the next event, so the events keep their chain.
|
|
9
|
+
- Updated dependencies [08beec5]
|
|
10
|
+
- Updated dependencies [48b7127]
|
|
11
|
+
- Updated dependencies [9541575]
|
|
12
|
+
- @procedures/client@0.48.2
|
|
13
|
+
- @procedures/collections@0.48.2
|
|
14
|
+
|
|
3
15
|
## 0.48.1
|
|
4
16
|
|
|
5
17
|
### Patch Changes
|