duckdb / duckdb/duckdb-node

Cannot open a READ_WRITE connection after a READ_ONLY connection even if it is closed

Open
#39 4 comments 0 reactions 0 assignees View on GitHub
Dominant language
C++
Stars
91
Forks
36
PR merge metrics
No merged PRs in 30d

Description

I might be doing something wrong here, but I'm wanting to use both READ_ONLY connections and READ_WRITE connections and even though it works most of the time there are cases where a READ_ONLY connection is ran first and once that happens any subsequent READ_WRITE connections fail to be created.

This is using Promises and async/await so I'm specifically waiting for connections to close before opening new connections as I know you can only have one READ_WRITE connection at a time.

Here is a Gist for example: https://gist.github.com/Rosslington/9aecbb3eb51386cd684cc6e538bfcfb9

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.