v0.14.0 Preview

[tantaman]

For JS & TS users the v0.14.0 preview release, and associated packages, are available under the next tag in npm.

"@vlcn.io/crsqlite-wasm": "0.14.0-next.0",
"@vlcn.io/direct-connect-browser": "0.4.0-next.1",
"@vlcn.io/direct-connect-common": "0.5.0-next.1",
"@vlcn.io/direct-connect-nodejs": "0.5.0-next.1",
"@vlcn.io/react": "2.4.0-next.1",
"@vlcn.io/rx-tbl": "0.13.0-next.0",
"@vlcn.io/xplat-api": "0.13.0-next.0",

Native binaries are available in the GitHub releases section: https://github.com/vlcn-io/cr-sqlite/releases/tag/v0.14.0-next.0

The vite-starter has been updated to use the v0.14.0-next.0 release.

Ever closer to the 1.0 release.

Improvements

• Reading and writing to/from crsql_changes is ~2.5x faster on average
• Flimsy string based encodings of column values have been removed, eliminating potential security concerns
• An issue in WebKit that would cause > 500% CPU usage when running the JIT on the WASM bundle has been worked around by changing compiler flags from Oz to O3. change optimization level of the wasm build to work around webkit jit… #268
• group by, distinct and other aggregate functions now work against crsql_changes

Possibly Breaking Change 1

If you have rolled your own networking layer two things have changed that will break it:

1. The value column in crsql_changes now returns the value as the correct type rather than a string encoded version of the value
2. The pk column in crsql_changes now returns a binary packed version of the underlying primary keys of the row

If you have not rolled your own networking layer there's nothing to worry about.

Possibly Breaking Change 2

The algorithm for breaking ties has changed slightly. If you have a peer to peer configuration where not all peers have converged before applying this latest update, you could see some inconsistency. The inconsistency would be resolved after users edit any fields which happened to be assigned exactly the same version on different peers.

Client-server configurations shouldn't be impacted.

Next Priorities

• Fugue Implementation investigate sequence / text crdts #65
• Improve auto-migration stability
• Recycling primary keys / re-inserting deleted items fixup delete tracking to allow re-insertion of the deleted item #71
• Improved CRR creation syntax via virtual tables Use CREATE VIRTUAL TABLE rather than select crsql_as_crr #181
• Primary key modifications modifying a primary key should record a delete as well as a create #50