Open rpbouman opened 6 months ago
Attached is a screenshot to illustrate the output of the repro path snippet given above: As you can see, the connection.query call results in a log message, but the preparedStatement.query call does not.
Thanks a lot for opening both issues and providing easy reproductions
What happens?
I am using duckdb WASM in the browser. The instantiation and setup matches the recommendations found in the documentation here https://duckdb.org/docs/api/wasm/instantiation
When I use connection.query, I see a message in the console which contains useful information like timestamp and statement. When I prepare a statement and call query on the prepared statement, no such logging appears.
It was expected that calling query on a preparedStatement would result in a message being logged, just like happens for connection.query.
To Reproduce
This is the setup code adopted from https://duckdb.org/docs/api/wasm/instantiation:
The following snippet demonstrates the issue against the setup shown above:
Browser/Environment:
Version 120.0.6099.130 (Official Build) (64-bit)
Device:
Windows 11 Desktop
DuckDB-Wasm Version:
1.28.0
DuckDB-Wasm Deployment:
https://cdn.jsdelivr.net/npm/@duckdb/duckdb-wasm@1.28.0/+esm
Full Name:
Roland Bouman
Affiliation:
EPAM Systems BV Netherlands