nedb-engine-client 2.8.4 → 2.8.6
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/README.md +20 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -9,6 +9,26 @@ Connect to any running `nedbd` instance from Node.js or the browser. No engine e
|
|
|
9
9
|
|
|
10
10
|
---
|
|
11
11
|
|
|
12
|
+
---
|
|
13
|
+
|
|
14
|
+
## ⚠️ Upgrade your server to nedbd 2.8.6
|
|
15
|
+
|
|
16
|
+
This client talks to `nedbd`, so its durability comes from the server. **2.8.6 fixes three defects in
|
|
17
|
+
2.8.5 and earlier** — a flush that hit a full disk silently discarded acknowledged writes, flush
|
|
18
|
+
failures were unobservable, and `nedb-cli repair` could not actually rebuild a damaged id index.
|
|
19
|
+
|
|
20
|
+
If a database ever returned rows and now returns none while `/verify` reports every object healthy,
|
|
21
|
+
that is the lost-id-index symptom and it is recoverable:
|
|
22
|
+
|
|
23
|
+
```bash
|
|
24
|
+
nedb-cli repair ./data
|
|
25
|
+
```
|
|
26
|
+
|
|
27
|
+
Replication consumers paging `/since`: gate historical catch-up on **`seq_index_ready`** from
|
|
28
|
+
`/status`, not on `scan_complete`. `scan_complete` is true on a warm boot precisely because the scan
|
|
29
|
+
was skipped, and before 2.8.6 `since` reported `has_more: false` in that state — which reads as
|
|
30
|
+
"caught up" on a database with every record unread.
|
|
31
|
+
|
|
12
32
|
## Install
|
|
13
33
|
|
|
14
34
|
```bash
|