fix: Syncing After Uploads when using Triggers

[stevensJourney]

Overview

When using triggers (e.g., database.triggers.createDiffTrigger()), the updateLocalTarget() method could fail to read the ps_crud sequence value, causing sync to be blocked after performing uploads.

Root Cause

The trigger system creates temporary tables and triggers (CREATE TEMP TABLE and CREATE TEMP TRIGGER) in the temp schema on the connection. When these temporary objects exist, SQLite's schema resolution mechanism prioritizes the temp schema when resolving unqualified table names. This means that queries to sqlite_sequence without an explicit schema qualifier could resolve to temp.sqlite_sequence instead of main.sqlite_sequence, returning no rows even though the sequence was actually advancing correctly.

Solution

Explicitly qualify sqlite_sequence queries with the main. schema prefix in SqliteBucketStorage.updateLocalTarget():

• Changed SELECT seq FROM sqlite_sequence → SELECT seq FROM main.sqlite_sequence

This ensures we always query the main database's sequence table, regardless of temporary schema context.

closes #778

[changeset-bot]

🦋 Changeset detected

Latest commit: f3ea146

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 8 packages

Name	Type
@powersync/common	Patch
@powersync/adapter-sql-js	Patch
@powersync/node	Patch
@powersync/op-sqlite	Patch
@powersync/react-native	Patch
@powersync/tanstack-react-query	Patch
@powersync/web	Patch
@powersync/diagnostics-app	Patch

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

[rkistner]

Great find! I would never have guessed this could be the cause.

Coukd there be any other places in our codebase affected by this type of issue? I.e. any other queries where we should add the main prefix to be safe?

[stevensJourney]

Great find! I would never have guessed this could be the cause.

Coukd there be any other places in our codebase affected by this type of issue? I.e. any other queries where we should add the main prefix to be safe?

This certainly had me scratching my head for a while before I found it.

The only other thing in this codebase I could think of are the queries to sqlite_master here and here - however in testing it seems like querying sqlite_master includes the data for the main database.
There might be some cases in the Rust core - I'm not very familiar with that codebase though, I could not see any glaring issues at a glance.