I have never used an actual db in my life.
I always just query vectors like this

Simplicity
Speed
Security
Version Control
Maintenance
Portability
Less expense (server)

Fullblown databases are unnecessary for most data storage needs, and for most processes that create data that needs to be stored, it's easier to make flat files.

That said it's usually pretty easy to know ahead of time when you're going to need to make complex queries and a full db is necessary

>>54393034
a "real" (legacy) DB doesn't really add much in terms of performance these days unless you have really big data sets in which case you are better off using some kind of "cloud" data store anyway.

For my own programs I store everything in flat files where possible. JSON or CSV mostly. I can't stand programs that store there resources (configs, data, etc) in obfuscated/binary files for no reason.

On a modern computer you can search a 50MB flat data file in under a second. desu even sqlite is overkill for most things.

>>54393034
it the layer doesnt cache anything it's not worth using on a multiple user system

I've created a few flatfile databases and used them on websites. CMS, MVC and even used one for a flatfile imageboard. I like them personally.

>>54393034
How to save Input that have tabs in them?

>>54396649
Flip the space bits to tabs

>>54393034
I use xml for most of what in doing. There's just no need for the complexity of a full database when only two or three items get changed, and read a few times.

>>54393034
i would rather use sqlite, tyvm