4 ms·
If a filesystem is a poor match for an email database, I'd appreciate the use of a well-established, open, and documented database format. That is, a format not
by nine_k 10y ago
If a filesystem is a poor match for an email database, I'd appreciate the use of a well-established, open, and documented database format. That is, a format not only your unique email client can understand. Something with an independent manipulation tool. In the perfect case, something that can be interoperably used by several different email clients (not in parallel, of course) and / or third-party indexing / filtering / other processing tools.
SQLite is used in many cases to store smaller things. It's likely not a good fit for a few gigabytes of email with binary attachments, though. I wonder what would be? NoSQL document-storing databases seem to have been created for a purpose like this. Is any of these used by any remotely popular client?
- ksk 10y ago>I wonder what would be? Well, maybe the people writing email clients have already thought quite a bit on this topic, likely created several prototypes, benchmarked them and chosen one that works the best given their constraints and features. Now all that's left is to open the format specification :)
- 616c 10y agoAgain, shoving everything into one file is mbox, which is a recognized file format (if not database), and it does not help things that much. I have wondered the Sqlite thing myself beyond my one criticism. If anything, you would love K9 Mail on Android, which does this out of necessity. And some people have made SQL and noSQL email stores. http://nosql.mypopescu.com/post/3083070885/couchdb-as-email-store http://nosql.mypopescu.com/post/3083070885/couchdb-as-email-... https://www.npmjs.com/package/haraka-nosql https://www.npmjs.com/package/haraka-nosql http://www.dbmail.org/ http://www.dbmail.org/