Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update faq.md | changed wording around prepared statements in FAQ #468

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
+1 −4
Open

Update faq.md | changed wording around prepared statements in FAQ #468

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions docs/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -12,10 +12,7 @@ subsequently should show up in your exception monitoring software.

## Does Supavisor support prepared statements?

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.
It currently supports prepared statements only in session mode.

## Why do you route connections to a single Supavisor node when deployed as a cluster?

Expand Down
Loading