Posted: Mon Apr 09, 2007 7:42 amin the "getting started example", the programcourses table has a primary key consisting of programcourses.programid WITH programcourses.courseid.
thats ok. but often in a dbschema, tables similar to programcourses will need to be a given a 'programcoursesid' which should be the primary key to uniquely identify programcourses records in possible other relationships with more tables inside the schema (generally programcourses would get extra fields added in that case too).
without checking the php's first, i tried and made a primary key for programcourses (called programcoursesid) and set the programcourses.programid+programcourses.courseid to be a "UNIQUE" pair (instead of the primary key).
i did not get the expected result
how would i solve a scenario like this? ; where a linktable like programcourses needs to be used itself in a relationship (and thus needs a primary key id field so it can be used as foreign key).
Scott.
thats ok. but often in a dbschema, tables similar to programcourses will need to be a given a 'programcoursesid' which should be the primary key to uniquely identify programcourses records in possible other relationships with more tables inside the schema (generally programcourses would get extra fields added in that case too).
without checking the php's first, i tried and made a primary key for programcourses (called programcoursesid) and set the programcourses.programid+programcourses.courseid to be a "UNIQUE" pair (instead of the primary key).
i did not get the expected result
how would i solve a scenario like this? ; where a linktable like programcourses needs to be used itself in a relationship (and thus needs a primary key id field so it can be used as foreign key).
Scott.