On Fri, May 14, 2010 at 03:01:39PM -0400, George Somers wrote: [edited for brevity]
> CREATE TABLE parent(parentID INTEGER PRIMARY KEY, ...); > > CREATE TABLE child(childID INTEGER PRIMARY KEY, fatherID INTEGER, ...); > > CREATE TABLE fatherChildActivity( > fcChildID INTEGER, > fcParentID INTEGER, > fcPlaysWhat TEXT, > FOREIGN KEY(fcChildID, fcParentID) REFERENCES child(childID, fatherID) > -- This foreign key make sure that 1) child exist, 2) father exist, > -- 3) father is really father of child. > ); Why do you need fatherChildActivity to make sure both, child and father exist when the existence of the child implies the existence of the father? Or can you have father-less child rows as long as the have no relations in fatherChildActivity? Nico -- _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
