Skip to content

Comments

docs: fix information about prepared statement support#468

Merged
v0idpwn merged 2 commits intosupabase:mainfrom
TheOtherBrian1:main
Jun 16, 2025
Merged

docs: fix information about prepared statement support#468
v0idpwn merged 2 commits intosupabase:mainfrom
TheOtherBrian1:main

Conversation

@TheOtherBrian1
Copy link
Contributor

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). It's worthwhile to add more context or remove the claim.

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

@TheOtherBrian1 TheOtherBrian1 requested a review from a team as a code owner November 3, 2024 19:01
@TheOtherBrian1 TheOtherBrian1 changed the title Update faq.md | session mode doc update Update faq.md | changed wording around prepared statements in FAQ Nov 3, 2024
@v0idpwn v0idpwn changed the title Update faq.md | changed wording around prepared statements in FAQ docs: fix information about prepared statement support Jun 16, 2025
@v0idpwn v0idpwn merged commit 88bbef3 into supabase:main Jun 16, 2025
33 of 36 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants