On Tue, 28 Feb 2017 19:44:56 -0700 "Keith Medcalf" <kmedc...@dessus.com> wrote:
> It has always been a requirement that FK relationships are 1:N > mappings, otherwise update anomalies will occur. If you have a > relational database that does not "naturally" have all FK > relationships as 1:N, then you have not normalized the data properly > (or sufficiently). If you say so. If by definition "sufficient" normalization has all FK relationships as 1:N, then by definition any design without that property is not sufficiently normalized. I tried with my relations P & C to show relation B is unnecessary. If you can show updating such a database would lead to update anomalies without B defined, I'd be interested to see that. --jkl _______________________________________________ sqlite-users mailing list sqlite-users@mailinglists.sqlite.org http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/sqlite-users
