You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
The value column in crsql_changes now returns the value as the correct type rather than a string encoded version of the value
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
For JS & TS users the v0.14.0 preview release, and associated packages, are available under the
next
tag in npm.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
Possibly Breaking Change 1
If you have rolled your own networking layer two things have changed that will break it:
value
column incrsql_changes
now returns the value as the correct type rather than a string encoded version of the valuepk
column incrsql_changes
now returns a binary packed version of the underlying primary keys of the rowIf 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
CREATE VIRTUAL TABLE
rather thanselect crsql_as_crr
#181Beta Was this translation helpful? Give feedback.
All reactions