It seems beneficial for my case. I have a light wrapper around SQLite called cq[1], to make querying CSVs with SQL more convenient. The point of the tool is to

It seems beneficial for my case. I have a light wrapper around SQLite called cq[1], to make querying CSVs with SQL more convenient. The point of the tool is to facilitate making ad-hoc, one-off queries on CSV data. CSVs don't specify the types of their columns, and they're either text or numeric. Having to be explicit on what the columns are would be a downside for me. Many CSVs have a ton of columns and I often care only about a few columns for one particular query I'll write and run once and never again. I've fallen into the trap[2] where imported columns compare alphabetically despite them being numbers. I've been casting in my queries and was considering adding argument syntax for specifying the types of certain columns, but now that I see this, I think the behavior on specifying everything as NUMERIC is more desirable. It's more like Excel/LibreOfficeCalc, where you can just use numbers and they behave like numbers without having to be super-explicit. [1] https://github.com/jolmg/cq https://github.com/jolmg/cq [2] https://news.ycombinator.com/item?id=28071615 https://news.ycombinator.com/item?id=28071615