3 ms·
Personally, I wouldn't trust today's sqlite files to be readable in 30 years. +1 to text-based formats. For long text I'd choose markdown. For anything with
by bjt 10y ago
Personally, I wouldn't trust today's sqlite files to be readable in 30 years.
+1 to text-based formats. For long text I'd choose markdown. For anything with a more nested structure, yaml. Yaml can do references between objects as well.
I'm not sure what you mean by "the kind of organisational power I'm looking for".
- avh02 10y agoWasn't aware yaml could do this, but in terms of organisational power, basically, my prime example which i've only mentioned at a high level so far would be to record all my travel information, because every time i have to fill out a visa form that asks, "which countries have you visited in the last 10 years" i usually end up going through passports. But this is the start for these things, I will later want to make indexes for photo/video archives, etc. but back to the example at hand: if i wanna know which year i went to country x, boom! query if i want to know where i went between 2005-2008, boom! query. if i want to know when i used a certain visa (e.g: multi-entry visas) boom! query. this gets difficult with flat files, not saying it's impossible with something like denormalised CSV, but i'd have to write my own scripts (or string together a frustrating sequence of bash commands) for these things.