On Wed, 2004-03-03 at 20:52, Jeff Cox wrote: > Dale, > First let me say I really appreciate you responding to my question. > Secondly, I would agree with you and in fact considered that possibility > early on in the design, but the truth is I need any given combination of > (SESSION_ID, SECTION_ID, ACTIVITY_ID) to be unique. I don't know of > another way to enforce this in the schema, except by making them the > primary key. If there is another way to do this my problem would > certainly be solved...
The <unique> stuff doesn't work? Wait, you need _any_combination_ of those three values to be unique? I don't get it. If any combination of those needs to be unique then you only need one number. Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
