The first place to start with DuckDB is in the terminal
Also a few other things to note:
1. The CLI is self-contained meaning no dependencies needed to be installed. It makes the process clean and easy
2. You mentioned timing commands. Simply run this dot command in the cli and then it will start providing execution times:
.timer on
I also added a note about this in the article and referenced this comment. It makes sense to get some extra info in there for the future readers. Thanks Matt!
OMG perfect thanks for that.
Good stuff. As an fyi with the duck, if you are exporting to parquet, you no longer need to specify the format arg afterwards e.g. this just works:
Copy v_orders to ‘data.parquet’
Only time you’d have to put in additional args is if you want to specify row group thresholds
Good call! They were still using the specifier in the docs so I thought I'd be verbose with it. But I love how brevity is always a focus for DuckDB.
Also a few other things to note:
1. The CLI is self-contained meaning no dependencies needed to be installed. It makes the process clean and easy
2. You mentioned timing commands. Simply run this dot command in the cli and then it will start providing execution times:
.timer on
I also added a note about this in the article and referenced this comment. It makes sense to get some extra info in there for the future readers. Thanks Matt!
OMG perfect thanks for that.
Good stuff. As an fyi with the duck, if you are exporting to parquet, you no longer need to specify the format arg afterwards e.g. this just works:
Copy v_orders to ‘data.parquet’
Only time you’d have to put in additional args is if you want to specify row group thresholds
Good call! They were still using the specifier in the docs so I thought I'd be verbose with it. But I love how brevity is always a focus for DuckDB.