You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I found an interesting issue when performing DuckDb testing. I had already performed testing using Sqlite in my environment and because of this the call to Eunomia::getDatabaseFile had download the data set and loaded it into a .sqlite file. When you do this you run into the following behavior:
What appears to be happening is that Eunomia sees the existing sqlite file and attempts to connect to it with the DuckDb driver. However there is an extension that allows DuckDb to use a sqlite file as a source called the sqlite_scanner which is not installed by default however can be installed in a DuckDb session. To resolve this issue the following code can be executed:
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I found an interesting issue when performing DuckDb testing. I had already performed testing using Sqlite in my environment and because of this the call to Eunomia::getDatabaseFile had download the data set and loaded it into a .sqlite file. When you do this you run into the following behavior:
What appears to be happening is that Eunomia sees the existing sqlite file and attempts to connect to it with the DuckDb driver. However there is an extension that allows DuckDb to use a sqlite file as a source called the sqlite_scanner which is not installed by default however can be installed in a DuckDb session. To resolve this issue the following code can be executed:
Once installed you can use the DuckDb driver to connect. An alternative is to delete the sqlite file and Eunomia will create it for you from scratch.
Beta Was this translation helpful? Give feedback.
All reactions