nate wrote: > You're not out of luck, you just need to add a primary key. The reason > for this is that composite primary keys are a monumentally *bad* idea.
Why exactly are they a bad idea ? They're used in many (serious) rdbms designs and are automatically constrained (which could of course be done with an explicit constraint). Cascades and other rdbms relationships & logic can be applied. Have you checked out: http://spyced.blogspot.com/2006/07/single-column-primary-keys-should-be.html http://blogs.ittoolbox.com/database/soup/archives/primary-keyvil-part-i-7327 (and yes i use postgresql, not mysql :-) but i only found this one after i read this post of yours. Just interested. After all, i might have a glaring stupidity in my rdbms design(s)) Albert --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Cake PHP" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/cake-php -~----------~----~----~----~------~----~------~--~---
