On Tue, Jan 14, 2020 at 9:35 AM Wout Mertens <wout.mert...@gmail.com> wrote: > On Mon, Jan 13, 2020 at 10:45 PM James K. Lowden <jklow...@schemamania.org> > This is a trade-off between schema simplicity, storage layout and speed of > some operations. I'd > argue that in this particular case, a JSON field is beneficial for > simplicity, speed and storage space.
+1. Echoes my own thoughts on this thread. James is right too of course, in the absolute, but limited denormalization for efficiency, and arguably for simplicity too, despite James' opinion, are valuable. Now it's "just" the matter of making the right tradeoff based on the particular circumstances, fully aware of the pros and cons. And that requires experience and knowledge (and testing/benchmarking, duh). Hopefully this particular thread will help people on this recurring topic. --DD _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
