> On Jan 12, 2020, at 4:12 PM, James K. Lowden <jklow...@schemamania.org> wrote: > > What is the motivation behind this advice? It's completely unnecessary.
Thanks for your opinion, James! I disagree. RFC822 headers are schemaless, and in a Usenet or email database they have rather high volume (probably 20+ per message) but go mostly unused. An NNTP server can't simply throw away the headers it doesn't need, but IMHO there are too many of them to do the usual SQL thing and add every header of every message to a table — that multiples the number of inserts and deletes by an order of magnitude. > For all the complexity JSON adds to the design, it adds exactly no power: > precisely the same effects can be achieved without it. Well sure, but you could say the same thing about indexes, couldn't you? I disagree about complexity. Encoding headers as JSON is pretty simple if you've got a JSON encoder handy, simpler than executing a SQL INSERT. And the JSON API is very easy to use. > I see no advantage to introducing JSON to a system with no external use for > it. Hm, a number of database companies (such as my employer, Couchbase) and their customers would disagree with you :) —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
