2
65%
main: 65%

Ran 16 Jun 2025 05:59PM UTC

Files 54

Run time 51s

Badge

Embed ▾

Committed 16 Jun 2025 05:49PM UTC coverage: 36.443% (-0.05%) from 36.492%

Job # 15688076777.2

Build Type

push

github

Committed by

web-flow

Commit Message

docs: fix information about prepared statement support (#468)

## What kind of change does this PR introduce?

doc update

## What is the current behavior?

Supavisor in transaction mode does not support standard prepared
statements, but the documentation claims otherwise.

## What is the new behavior?

Updated the FAQ

## Additional context

The docs state:

> As of 1.0 Supavisor supports prepared statements. Supavisor will
detect
`prepare` statements and issue those to all database connections. All
clients
will then be able to address those prepared statements by name when
issuing
`execute` statements.

Prepared statements are not fully supported and this claim caused user
confusion
([ticket](https://app.hubspot.com/live-messages/19953346/inbox/8310448973#email)).
It's worthwhile to add more context or remove the claim.

It's also worth re-opening up issue #69

Co-authored-by: felipe stival <14948182+v0idpwn@users.noreply.github.com>

Run Details

750 of 2058 relevant lines covered (36.44%)

112.05 hits per line

supabase / supavisor / 15688076777 / 2
65%
main: 65%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job run-integration - 15688076777.2

supabase / supavisor / 15688076777 / 2 65% main: 65%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job run-integration - 15688076777.2

supabase / supavisor / 15688076777 / 2
65%
main: 65%

README BADGES
x