Rich Shepard <rshep...@...> writes: > > On Wed, 9 Jun 2010, Oliver Peters wrote: > > > So I assume that it is not(!) a mistake not(!) to use a composite PK in my > > table "customer" (customernumber,customerorigin) and to refer to it from > > the table "order" where I had to use these fields as a composite FK? > > Oliver, > > Too many negatives there for me to really follow what you're asking.
sorry, I try my very best: adverted to the table customer I've 2 possible solutions and I ask myself if the first one is incorrect - the reason why I ask lies in the behaviour of my frontend (OpenOffice Base) that has problems to handle UNIQUE-Constraints under special circumstances (main-subform-connections) solution 1 ---------- CREATE TABLE customer( id INTEGER PRIMARY KEY AUTOINCREMENT, customernumber INTEGER, customerorigin INTEGER, name TEXT, UNIQUE(customernumber,customerorigin) ); solution 2 ---------- CREATE TABLE customer( customernumber INTEGER, customerorigin INTEGER, name TEXT, PRIMARY KEY(customernumber,customerorigin) ); thx for your patience Oliver _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
