In this case, rules can be made to be broken. In the case of larger blobs, I push those out to a different table, and enforce (Through my software, not a unique constraint as mentioned) the one-to-one relationship. There is no reason to keep the blob on a record that is queried constantly.
On Sat, Oct 14, 2017 at 6:37 AM, Richard Damon <rich...@damon-family.org> wrote: One way to make them build one to at-most-one relationships is too add a > unique index on the foreign key, then it can only occur once. > > A True one-one relationship by the normailization rules says that they > should all be in the same record. > > -- > Richard Damon > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@mailinglists.sqlite.org > http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users > _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
