To Reproduce

1. Open a Read/Write connection using SQLTools to a duckdb
2. (Don't run any queries)
3. Attempt to access the duckdb from another client

Expected result

Another client should be able to access the duckdb

(Assuming no read/write queries are currently running)

Actual result

A .wal file is generated for the db, suggesting there are changes to the DB that are yet to be commited

IO Error: Could not set lock on file "../../needful_things.duckdb": Resource temporarily unavailable

Extra Context

See #4

This is somewhat by design from duckdb, but we should be able to close the readwrite connection after a query has finished / when there are no queries running.

I think core SQLTools is doing something unexpected here on connection which

Workarounds

1. Either: Running any query from duckdb SQLTools seems to clear the .wal and close the connection
2. Or: Manually close the connection from the duckdb sidebar

it would be great if the extension would fully support remote development. e.g. the file browser always shows the local filesystem instead of the remote one when selecting the duckdb file.

I did not see any explanation in the description for this change in #12 - was it necessary? I did not see any vscode interfaces change in that PR, and only supporting the very latest VSCode is a little bit inconvenient for everyone who hasn't upgraded yet. Can this be reverted back to "^1.42.0" (or if it needs to be bumped, at least "^1.83.0"

Need to have it close the connection after query run:

I am getting the following error popup when I click on a table:

Request connection/GetChildrenForTreeItemRequest failed with message: Catalog Error: Table with name <table_name> does not exist! Did you mean "<schema>.<table_name>"?

There is a 0.9.2 release for DuckDB and apparently it has critical bugfixes

https://github.com/duckdb/duckdb/releases

When expanding the views branch of the explorer within a schema, all of the views present within the database are shown, rather than just the views that are in that particular schema.

Registering does not work for me, any ideas?

[1690808344855] INFO  (ls): REQUEST RECEIVED => ls/RegisterPlugin
[1690808344856] INFO  (ls): request to register plugin: "c:\Users\geoff\.vscode\extensions\evidence.sqltools-duckdb-driver-0.0.1\out\ls\plugin.js"
[1690808345187] ERROR (ls): Error registering plugin: {"code":"ERR_DLOPEN_FAILED"}
    error: {
      "code": "ERR_DLOPEN_FAILED"
    }
[1690808345192] ERROR (ext): ERROR: Error loading plugin DuckDB Driver for SQLTools Plugin Request ls/RegisterPlugin failed with message: \\?\c:\Users\geoff\.vscode\extensions\evidence.sqltools-duckdb-driver-0.0.1\node_modules\duckdb\lib\binding\duckdb.node is not a valid Win32 application.
\\?\c:\Users\geoff\.vscode\extensions\evidence.sqltools-duckdb-driver-0.0.1\node_modules\duckdb\lib\binding\duckdb.node, {"code":-32603}
    ns: "error-handler"

Hello! It would be great to fetch some bug fixes from 0.10.1 release. I can do it by myself when following blockers will be resolved.

Blocked by:

• Update duckdb-node: duckdb/duckdb-node#68
• Update duckdb-async: motherduckdb/duckdb-async#30

Problem

When connection to duckdb via an in memory connection and trying to do write operations (creature/update/delete). We get the following error:

Invalid Error: Cannot execute statement of type "CREATE" on database "<database_name>" which is attached in read-only mode!

Archie has pointed me to the code that is currently causing all in memory connections to only open sqltools-duckdb in read only: sqltools-duckdb-driver

Example use case of in memory

My use case is actually for an onboarding process I am setting up for some new hires. I have taken the work the dbt folk did for their jaffle-shop-template. I then just removed the dbt part so that potential hires can write some sql transformation (using no transformation tools).

I am sure there are some CI use case which could also benefit.

For reference i am working on this for Australia's NSW Department of Education onboarding for data people (they get given a range of tools such as duckdb and evidence): nsw_doe_data_case_study

Current limiation

We talked about just enabling a read-write setting for in memory connection.

The only downside is that while the connection is open, READWRITE locks the db.

Ideally a user would be able to have an open connection to duckdb via sqltools and then still access duckdb by evidence and other reporting tools.