fix(sync-rules): length() and instr() should count code points to match SQLite#693
Closed
sravan27 wants to merge 1 commit into
Closed
fix(sync-rules): length() and instr() should count code points to match SQLite#693sravan27 wants to merge 1 commit into
sravan27 wants to merge 1 commit into
Conversation
…ch SQLite
length() used JS String.length (UTF-16 code units) and instr() used
String.indexOf (UTF-16 index), so both diverged from SQLite for text
containing non-BMP characters (e.g. emoji): length('😀') returned 2
instead of 1, and instr() positions were shifted by non-BMP characters
before the match. Both now iterate by code point, matching SQLite and the
existing substring() behaviour. Blob handling (byte counts) is unchanged.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: 2e6fd14 The changes in this PR will be included in the next version bump. This PR includes changesets to release 17 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
|
Sravan Sridhar seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow-up to the
substring()code-point fix — the same UTF-16-vs-code-point divergence affects two sibling functions.Problem
length()used JSString.length(UTF-16 code units) andinstr()usedString.indexOf(a UTF-16 index), so both diverge from SQLite for text containing non-BMP characters (emoji, mathematical alphanumerics, etc.):length('😀')12length('a😀b')34instr('😀x', 'x')23Because sync-rule expressions are evaluated client-side and must agree with the source database, a filter like
length(name) > 10orinstr(...)over text containing emoji could include/exclude rows differently on the client than on the server — silent sync divergence.Fix
Both functions now iterate by code point (spreading the string / counting code points in the prefix), matching SQLite and the existing
substring()behaviour. Blob handling is unchanged (still byte counts, which is correct per SQLite).Tests
Added regression cases to
sql_functions.test.tsforlengthandinstrcovering non-BMP characters, including the case where a non-BMP character precedes the match (the one that actually diverges). Full sync-rules suite passes.Verified against the system
sqlite3as ground truth.🤖 Generated with Claude Code