On Tue, 7 Jan 2020 17:11:45 -1000 Jens Alfke <j...@mooseyard.com> wrote:
> Consider encoding the headers as JSON and storing them in a single > column. SQLite has a JSON extension that makes it easy to access > values from JSON data in a query. What is the motivation behind this advice? It's completely unnecessary. For all the complexity JSON adds to the design, it adds exactly no power: precisely the same effects can be achieved without it. I can understand the utility of using SQLite's JSON features where there's pre-existing JSON, especially if there's need to preserve it and reproduce it later. I see no advantage to introducing JSON to a system with no external use for it. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
