I tried using a database for personal notes many years ago and the problem I discovered was that I can't do a quick Ctrl+F to find previous scraps of knowledge.
Instead, I use plain "notes.txt" and use the editor's text search functions (including regex functionality) to locate things.
These 2 ways of finding text have very different ergonomics:
- SQL: select * from notes where description like '%ubuntu config%';
- text editor: Ctrl+F "ubuntu config" <press Enter>
Yes, one can write a program to "dump" the SQL database to a text file for subsequent search by a text editor. The problem is that it creates a read-only file that you can't edit-in-place. And one can also write a custom wrapper program in whatever language as a GUI for the database but now we're way past your simply "reply to email" paradigm and expending a lot of effort in "yak shaving" instead of just taking notes.
Not saying your system is bad for you but I'm guessing that most people would find the friction of a SQL database too high for freeform notes.
SQLite has full-text search built-in (including tokenization of english words with similar roots). It takes just a few statements to enable, and it can even do spelling corrections with an optional extension.
> most people would find the friction of a SQL database too high for freeform notes
Something that I find not only true, but inherent in relational databases: they require some kind of schema, and schemas for freeform text and ideas are notoriously difficult.
I created my own software, which doesn't have a fancy gui or anything, but organizes my notes sufficiently for me, using plain markdown files and dumping the contents into an ElasticSearch index configured for text analysis. I can easily do a very good full text search on the body of the notes, plus I've indexed the keywords for each note in their own mapping.
In addition to having good linking together of related ideas, wiki-like, it's good to have the ability to fruitfully search without the restrictions of exact term matches. Even relatively simple things like stemming and common synonym matching* can improve the usability of a large collection of notes measurably.
*No, I don't think we've really solved the searching by synonym problem. More work is needed.
It would be extremely easy to replace storing in a db with append to a text file. (As a matter of fact it already appends everything to a text file for added security...)
However I kind of like the fact that it's hard to edit, and I (almost) never do it. It's a log -- the log of my brain.
Also, append (or prepend) to a text file means everything is in the order it was written. But sometimes I miss a day and then come back to write about days out of order (I write about Tuesday, then about Monday).
With a db it is trivial to order posts either in the order of the days or in the write order, etc. With only a text file that would be very difficult.
I tried using a database for personal notes many years ago and the problem I discovered was that I can't do a quick Ctrl+F to find previous scraps of knowledge.
Instead, I use plain "notes.txt" and use the editor's text search functions (including regex functionality) to locate things.
These 2 ways of finding text have very different ergonomics:
- SQL: select * from notes where description like '%ubuntu config%';
- text editor: Ctrl+F "ubuntu config" <press Enter>
Yes, one can write a program to "dump" the SQL database to a text file for subsequent search by a text editor. The problem is that it creates a read-only file that you can't edit-in-place. And one can also write a custom wrapper program in whatever language as a GUI for the database but now we're way past your simply "reply to email" paradigm and expending a lot of effort in "yak shaving" instead of just taking notes.
Not saying your system is bad for you but I'm guessing that most people would find the friction of a SQL database too high for freeform notes.