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

support "PREPARE" statement and "EXECUTE " statement #234

Open
Leo-XM-Zeng opened this issue Sep 30, 2024 · 1 comment
Open

support "PREPARE" statement and "EXECUTE " statement #234

Leo-XM-Zeng opened this issue Sep 30, 2024 · 1 comment
Labels
bug Something isn't working
Milestone

Comments

@Leo-XM-Zeng
Copy link
Contributor

Current Behavior

postgres=# create extension pg_duckdb;
WARNING:  To actually execute queries using DuckDB you need to run "SET duckdb.execution TO true;"
CREATE EXTENSION
postgres=# SET duckdb.execution TO true;
SET
postgres=# SELECT COUNT(*) FROM t;
 count 
-------
  1000
(1 row)

postgres=# PREPARE test_stmt AS SELECT COUNT(*) FROM t;
PREPARE
postgres=# EXECUTE test_stmt;
 count 
-------
     0
(1 row)
@JelteF JelteF added the bug Something isn't working label Sep 30, 2024
@JelteF JelteF added this to the 0.2.0 milestone Sep 30, 2024
@JelteF
Copy link
Collaborator

JelteF commented Oct 1, 2024

Thanks for the bug report. That's indeed something we should fix. However, the usage of prepared statements at the SQL level (i.e. PREPARE/EXECUTE queries) is a lot lower than at the protocol level (Parse/Bind/Execute messages). So I don't consider this a blocker for 0.1.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants