[simolus3]

When a COMMIT for a transaction fails, we issue a ROLLBACK statement instead to revert the transaction. Because TransactionImplementation can only issue one of those statements however, the rollback() call had no effect. This avoids the issue by running the ROLLBACK statement directly against the underlying context.

A similar issue exists in the Kysely driver, where we've always resolved the writeTransaction() callback. Kysely calls rollbackTransaction() if a prior commitTransaction call failed, our current setup there sets this.#tx = null too early and swallows the error. For consistency, this changes the Kysely implementation to forward errors as well.

Closes #1176.

AI use: Claude found the Kysely issue while reviewing the other change, I also used Claude to fix it.

[changeset-bot]

🦋 Changeset detected

Latest commit: 052b3b7

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

This PR includes changesets to release 7 packages

Name	Type
@powersync/kysely-driver	Patch
@powersync/common	Patch
@powersync/node	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