3 ms·
Actually, why not both? Why not have files and an database like interface for them? Even better, databases normally provide a query plan explanation, quite li
by genman 3y ago
Actually, why not both?
Why not have files and an database like interface for them?
Even better, databases normally provide a query plan explanation, quite like what is demanded here.
- indymike 3y agoI once thought the same, but there is not a universal answer on how to store data that delivers the combination of performance, reliability for every use case. Files are the lcd and leave room for optimization - and end up being a nice abstraction to hide the inner workings of decades of different storage devices and apis.
- tqwhite 3y agoThough I use .ini, myself. I often think about changing to sqlite. It is insanely stable and provides all the goodness of a database. Since I speak SQL like a native, it would be easy for me to manage. But, I stick with .ini still because, 1) I have a great access module that I would have to rewrite and, 2) there's always a text editor and sometimes I'd have to add a sqlite UI. Sounds like work to me.