Kotlin: Test a mutation without committing it

Executes the mutation but rolls back the transaction instead of committing it, so no changes are persisted.

• The mutation runs and its result (including side effects such as triggers) is returned in the response, but the transaction is rolled back afterward.
• Useful for testing mutations without touching real data.
• Requires PostgREST's db-tx-end setting to allow client-controlled transaction rollback.

Examples

With `update()`

val toUpdate = City(name = "Mordor")
supabase.from("cities").update(toUpdate) {
    filter {
       City::name eq "Gondor"
    }
    dryRun()
}
// Row is not actually updated in the database.