Re: Single vs Multiple primary keys

2005-05-16 Thread Daniel Walker
On Sunday 15 May 2005 20:31, Dan Bolser wrote: > You must mean a multipart primary key with three parts :) > > or "multiple-column indexes" > > That is what I would do (use a multiple-column index (primary key) - its > kinda based on opinion, but I think you should let the real data be the > prima

Re: Single vs Multiple primary keys

2005-05-15 Thread Dan Bolser
On Sun, 15 May 2005, Martijn Tonies wrote: >Bob, > >> I have a table, see below, that contains a single primary key >(SubTestCaseKey ) and a number of foreign keys >> >> * plantriggers_ID_FK , >> * testcase_root_ID_FK >> * testcasesuffix_name_FK >> >> What I want to ensure is that there are no dup

Re: Single vs Multiple primary keys

2005-05-15 Thread Martijn Tonies
Bob, > I have a table, see below, that contains a single primary key (SubTestCaseKey ) and a number of foreign keys > > * plantriggers_ID_FK , > * testcase_root_ID_FK > * testcasesuffix_name_FK > > What I want to ensure is that there are no duplicate records when considering the three foreign keys

Single vs Multiple primary keys

2005-05-15 Thread Bartis, Robert M (Bob)
I have a table, see below, that contains a single primary key (SubTestCaseKey ) and a number of foreign keys * plantriggers_ID_FK , * testcase_root_ID_FK * testcasesuffix_name_FK What I want to ensure is that there are no duplicate records when considering the three forei