3 ms·
Honestly pretty strange to write a package manager for sqlite and to use directories + json files to store the data instead of sqlite.
by david2ndaccount 3y ago
Honestly pretty strange to write a package manager for sqlite and to use directories + json files to store the data instead of sqlite.
- gosenx 3y agoGreat point
- gjvc 3y agolocal system log "files" and package databases would be an excellent example of using sqlite
- grumblingdev 3y agoSQL not so good for tree structures. Recursive CTEs are pretty gnarly. Graphdb would be ideal.
- jeremyjh 3y agoYou want to bring in a dependency to avoid writing one 8 line CTE?
- christophberger 3y agoThe number of lines needed is not a good measure for gnarliness. (To be fair, I don't know if gnarliness is measurable at all.)
- jeremyjh 3y agoIt isn’t gnarly at all, but recursive CTE are outside the experience of most SQL devs. Here “gnarly” is used to describe “unfamiliar”.
- jbverschoor 3y agoSQLite is a pretty darn good solution for any file(set) that needs atomic / consistent writes
- edgyquant 3y agoWhy not? Just add child/parent ids
- nalgeon 3y agoA couple of reasons: 1) I wanted human readable specs and lockfiles. 2) I didn't want to introduce a dependency (working with SQLite in Go is pretty ugly, it either requires GCC or a ton of other dependencies for a pure Go implementation).