Use parameterized queries to select SQL schemas. #11356
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
dosubot
bot
added
the
🤖:improvement
|
I haven't been able to figure out how to do this properly for the duckdb driver, opened an issue: Mause/duckdb_engine#796 |
obi1kenobi
force-pushed
the
pg/use-parameterized-queries
branch
from
6667ac4 to
c0f7c10
Compare
nfcampos
approved these changes
Oct 4, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This switches to parameterized queries for selecting schemas for all databases, except DuckDB for which I wasn't able to figure out how to get parameterized queries to work: Mause/duckdb_engine#796
For all the other databases, I followed the parameterized query approach described by their docs.