Wrong: use csv
Correct: use sqlite
This is the tl;dr of an upcoming blog post. If you have any questions about this choice please ask them so I can address them.
I realize that very often the csv is an export from Excel, done by people who wouldn't be able to create a SQLite database. But when it gets exported from some other software as a "reporting feature" or "export feature" there's no excuse.
@stchris I agree
@stchris Recently I've been exporting or collating data from APIs into sqlite and using metabase to help non technical users query the data from there. It's working very well so far and much better than exporting to CSV to load in Excel.
@Dignz exactly. And Metabase is really good! It was a pleasure setting it up and seeing non-devs pick it up and see its value.
@stchris if going for sqlite then why not go further with mysql which doesn't fall down so easily
@tomosaigon what do you mean with "fall down"?
One typical use case of a csv file is "Tom can you pass me the current state of blah". I'm advocating for a sqlite file instead of a csv file. MySQL is a whole different ball game in terms of sending data around
@steko hm, interesting. I'll check it out, thanks
@stchris thank you!
Fosstodon is an English speaking Mastodon instance that is open to anyone who is interested in technology; particularly free & open source software.