Thread

yes, i think the correct way would be to create a duckdb instance, use the connect method from nsd to instantiate it, and then with the same connection use the mysql extension to read or perform operations in the other db. you will have your mysql db and other duckdb db wired up by the same connection. i'm implementing something similar in relatr but in a single duckdb db, to have the nsd tables and other relatr specific metadata tables in the same db using a shared connection, as it is how duckdb recommends to manage concurrency. That also gives me the possibility to use the nsd tables to do any sql query crossing all