fix: OP-sqlite write transaction single operation notification

[Chriztiaan]

This PR addresses a timing issue in OPsqlite where the SQLite update hook triggers before the commit completes when performing single-write transactions (Resulting in ps_crud not being processed). As a result, nextCrudItem was returning undefined because the data was not yet committed at the time the hook fired.

Using react-native-quick-sqlite as reference, updates are now batched and only flushed after a write lock is released.

[changeset-bot]

🦋 Changeset detected

Latest commit: 8441600

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

This PR includes changesets to release 1 package

Name	Type
@powersync/op-sqlite	Minor

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]

Changes look good.

I assume this would also affect regular watched queries?

[Chriztiaan]

Changes look good.

I assume this would also affect regular watched queries?

Using const { data: psCrud } = useQuery("Select * from ps_crud") initially I could see that it was stuck at 1, but its definitely becoming 0 now after being processed. I verified that powersync.watch also triggers with the expected results.

It does improve watched queries and the reactive query hooks.

[rkistner]

I mean that if you had useQuery('select * from my_table'), you could potentially get outdated results before because of the same issue, and that should be fixed now.

[Chriztiaan]

I mean that if you had useQuery('select * from my_table'), you could potentially get outdated results before because of the same issue, and that should be fixed now.

Correct - sorry I misunderstood. Updated the changeset entry to mention this.