I started using the driver more and I noticed one potential issue and have a suggestion:
Issue
Although I enabled the "read-only" button, the duckdb file is still locked by metabase. In my case, this is not very blocking: I detect it and restart the metabase docker, which solves the problem.
Suggestion
It would be nice to have extra params directly on the connection page: memory_limit and threads, to be able to control the resources that the duckdb driver is allowed to use.
it is possible to set them in a query via an sql question, but I find it quite "dirty".
Otherwise, it works like a charm and it's quite amazing to have the speed of duckdb in metabase!
Hello Alex,
I started using the driver more and I noticed one potential issue and have a suggestion:
Issue Although I enabled the "read-only" button, the duckdb file is still locked by metabase. In my case, this is not very blocking: I detect it and restart the metabase docker, which solves the problem.
Suggestion It would be nice to have extra params directly on the connection page:
memory_limit
andthreads
, to be able to control the resources that the duckdb driver is allowed to use. it is possible to set them in a query via an sql question, but I find it quite "dirty".Otherwise, it works like a charm and it's quite amazing to have the speed of duckdb in metabase!
Thanks again for the work here! best, Luc