firebird-wasm 0.4.0 → 0.4.1
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 +18 -0
- package/dist/wasm/firebird-embedded.wasm +0 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,24 @@ All notable changes to `firebird-wasm`. This project follows
|
|
|
4
4
|
[semantic versioning](https://semver.org/); while the major version is 0 the
|
|
5
5
|
API may still move between minor releases.
|
|
6
6
|
|
|
7
|
+
## 0.4.1 — 2026-10-10
|
|
8
|
+
|
|
9
|
+
### Changed
|
|
10
|
+
|
|
11
|
+
- **`execBatch` runs on Firebird's `IBatch`.** The rows' messages are packed
|
|
12
|
+
at the metadata's aligned stride into one buffer and handed to the engine as
|
|
13
|
+
one batch request, where 0.4.0 executed the prepared statement once per row.
|
|
14
|
+
Measured in Node on the same artifact build: 5,000 rows of five columns take
|
|
15
|
+
41–55 ms (65–71 ms in 0.4.0; 127–136 ms as one `exec()` per row inside a
|
|
16
|
+
transaction). In `firebird-quake2`'s map load, which 0.4.0's batch had left
|
|
17
|
+
13 % slower than its PSQL chunk loaders (each row was still a statement
|
|
18
|
+
execute inside the engine, while a procedure's `INSERT` is a node of one
|
|
19
|
+
compiled request), the batch is now 5 % faster than those loaders, with
|
|
20
|
+
the 37,000-row `face_verts` table a quarter faster. The row that fails is
|
|
21
|
+
still named, the record count still covers the whole batch, and a statement
|
|
22
|
+
without parameters still runs once per row. Needs a rebuilt artifact: the
|
|
23
|
+
TypeScript is unchanged.
|
|
24
|
+
|
|
7
25
|
## 0.4.0 — 2026-10-10
|
|
8
26
|
|
|
9
27
|
### Added
|
|
Binary file
|
package/package.json
CHANGED