A Minimalist Guide to SQLite
tech.marksblogg.com
A Minimalist Guide to SQLite
1–10 of 127 posts
Re: A Minimalist Guide to SQLite
#2I feel this article misses out on "why". I tend to store stuff as csv or json, then slurp it into python to operate on it. It's not clear what benefit putting your csv into sqlite gets you, from this article.
Re: A Minimalist Guide to SQLite
#3I feel this article misses out on "why". I tend to store stuff as csv or json, then slurp it into python to operate on it. It's not clear what benefit putting your csv into sqlite gets you, from this article.
For one, memory usage. You either have to load your entire CSV file into memory or read it line-by-line in order to get the result you're looking for. SQLite intelligently uses disk, memory and indexes for that purpose.
Plus, you know, the whole SQL thing.
Re: A Minimalist Guide to SQLite
#4I feel this article misses out on "why". I tend to store stuff as csv or json, then slurp it into python to operate on it. It's not clear what benefit putting your csv into sqlite gets you, from this article.
sounds wasteful and slow for anything larger than a few MB compared to the awesome (really) sqlite
Re: A Minimalist Guide to SQLite
#5I feel this article misses out on "why". I tend to store stuff as csv or json, then slurp it into python to operate on it. It's not clear what benefit putting your csv into sqlite gets you, from this article.
An explanation of the considerable benefits that relational databases bring to a wide class of problems is beyond the scope of an article on one particular implementation, and also beyond the scope of an HN comment.
Re: A Minimalist Guide to SQLite
#6I feel this article misses out on "why". I tend to store stuff as csv or json, then slurp it into python to operate on it. It's not clear what benefit putting your csv into sqlite gets you, from this article.
SQLite is when the data is a little too big for your approach, but not worth the hassle of installing/running/managing a database process.
The flat files method may lead to partial or empty files in certain failure cases (crash during writes) that may or may not be more gracefully handled by SQLite.
Re: A Minimalist Guide to SQLite
#7I feel this article misses out on "why". I tend to store stuff as csv or json, then slurp it into python to operate on it. It's not clear what benefit putting your csv into sqlite gets you, from this article.
So you can insert/delete/update records without rewriting the whole file. And you get many other features like transaction, spill cache pages, fflush & fsync behind the scenes.
Re: A Minimalist Guide to SQLite
#8I feel this article misses out on "why". I tend to store stuff as csv or json, then slurp it into python to operate on it. It's not clear what benefit putting your csv into sqlite gets you, from this article.
Sibling comments are on target but also the "relational" advantages of storing your data in a database.
Re: A Minimalist Guide to SQLite
#9I feel this article misses out on "why". I tend to store stuff as csv or json, then slurp it into python to operate on it. It's not clear what benefit putting your csv into sqlite gets you, from this article.
"SQLite As An Application File Format" [0] and "What If OpenDocument Used SQLite?" [1], both by the author of SQLite, may help to answer why you'd use it over other file serialization formats, such as CSV, JSON, Python's pickle, etc.
Re: A Minimalist Guide to SQLite
#10I feel this article misses out on "why". I tend to store stuff as csv or json, then slurp it into python to operate on it. It's not clear what benefit putting your csv into sqlite gets you, from this article.
An sqlite db file is probably as light as your json or csv AND better formed/typed