@loradb/lora-wasm 0.17.0 → 0.19.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.
- package/README.md +8 -0
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -255,6 +255,14 @@ public surface — consumers can swap backends without rewriting types.
|
|
|
255
255
|
- The wasm module runs inside one JavaScript runtime. Auto-commit reads can
|
|
256
256
|
overlap on engine snapshots; write commits serialize. Use more Workers for
|
|
257
257
|
separate graphs or stronger UI isolation.
|
|
258
|
+
- A write stream (`db.stream(...)` or `openExportStream(...)` over a query
|
|
259
|
+
that writes) runs in a hidden transaction that holds the writer until it
|
|
260
|
+
is read to the end or closed, and only then commits. Writes started
|
|
261
|
+
meanwhile (`execute`, `transaction`, another write stream, imports,
|
|
262
|
+
`clear`, `loadSnapshot`) reject with `LORA_TRANSACTION` instead of
|
|
263
|
+
waiting, because the only thread that could release the writer is the
|
|
264
|
+
one asking for it. Reads keep working. `transaction()` itself runs
|
|
265
|
+
synchronously, so any number of concurrent calls simply run in turn.
|
|
258
266
|
- I64 values are delivered as JS `number` and lose precision above 2^53.
|
|
259
267
|
Applications that need bigint precision should use the native
|
|
260
268
|
`lora-node` binding instead.
|