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. You can even index them.
Simon’s suggestion (a row per header) is correct in theory, but the large numbers of headers you’ll be storing in an NNTP database will make that approach pretty expensive, I think. (I’ve mostly given up on relational-database orthodoxy, and doing so helped make version 2 of my program about 5x faster than version 1.) —Jens _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
