duckdb-node icon indicating copy to clipboard operation
duckdb-node copied to clipboard

Closing a connection fails

Open dusadrian opened this issue 1 year ago • 3 comments

Hi all,

This is an issue following this DuckDB discussion, and it might also be related to Issue: https://github.com/duckdb/duckdb-node/issues/39

What happens is, after successfully closing a connection the first time, any subsequent connection cannot be closed anymore. To reproduce, please clone this quick repo.

After the usual npm install to get all necessary node packages, use npm start to start the application and push the button. After no longer than 30 seconds, the database lock is released and I can connect using either CLI from the Terminal, or from another API such as the duckdb package in R.

However, after the first lock being released, for any subsequent button push (therefore any subsequent database connection), the lock is not released anymore no matter how much time one waits.

This was tested on MacOS on both Intel and ARM computers, using Sonoma. The DuckDB version is the latest, 0.10.0 (as per the package.json file in the above repo.

In hoping this can be reproduced, Adrian

dusadrian avatar Feb 25 '24 12:02 dusadrian

I am having the exactly issue with v0.8.1 & the latest versions. I was tested on MacOS also.

jeffreytkj avatar Feb 28 '24 06:02 jeffreytkj

any updates? I'm facing the same problem. I try to create a database on the fly and then export the whole database file.

t-samuelg avatar Mar 25 '24 13:03 t-samuelg

Confirm, can reproduce on macOS and inside docker containers of all sorts

hilkeheremans avatar Jun 24 '24 13:06 hilkeheremans