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

Don't plan twice for prepared statements #229

Open
JelteF opened this issue Sep 30, 2024 · 0 comments
Open

Don't plan twice for prepared statements #229

JelteF opened this issue Sep 30, 2024 · 0 comments
Labels
performance We need more speed
Milestone

Comments

@JelteF
Copy link
Collaborator

JelteF commented Sep 30, 2024

In #147 we added support for prepared statements, but that was done planning the query twice in DuckDB, once during planning to get the the column types of the result and once during execution. While this works, it's clearly suboptimal performance wise, and it's something we should change eventually.

@JelteF JelteF added long-term performance We need more speed labels Sep 30, 2024
@JelteF JelteF added this to the Long term milestone Sep 30, 2024
@JelteF JelteF removed the long-term label Sep 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performance We need more speed
Projects
None yet
Development

No branches or pull requests

1 participant