> On Jan 13, 2020, at 1:45 PM, James K. Lowden <jklow...@schemamania.org> wrote: > > So, basically, a nomalized design requires too much use of INSERT? > You're making an efficiency argument here, or maybe > ease-of-implementation assertion. For me, inserting one header row or > 20 is the same coding effort (still need a loop).
I was suggesting _zero_ header rows, i.e. store the headers as a blob column in the messages table, instead of having a separate table. > I think transaction throughput would be about the same if COMMIT is applied > only to whole messages. There are other pain points. From what I've seen in the past, IIRC one of them is managing the foreign-key constraints (e.g. SQLite finding and deleting header rows when a message row is deleted), and the necessity of using JOINs to get at the headers. Anyway: I merely said to "consider encoding the headers as JSON". Certainly didn't mean to imply it was the canonical answer. —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
