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.

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

explicit prepared statement support #86

Open
glyph opened this issue Mar 28, 2024 · 0 comments
Open

explicit prepared statement support #86

glyph opened this issue Mar 28, 2024 · 0 comments

Comments

@glyph
Copy link
Owner

glyph commented Mar 28, 2024

By constraining all of its SQL into a small, pregenerated set of static strings, DBXS makes it easier for drivers like sqlite3 and psycopg whose default prepared statement support is to simply maintain a fixed-size cache of statements.

However, this support is presently accidental. Although those drivers support tuning the cache size, and DBXS has the ability to enumerate all of the queries that all loaded accessors support ahead of time as long as they've all been imported, we don't provide any hints to those drivers. Similarly, drivers like MySQL which require an explicit preparation step are not supported.

DBXS should press this performance advantage more, and add explicit support and testing to ensure that prepared statements are being used everywhere.

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

No branches or pull requests

1 participant