Taken from the standpoint of an SQL engineer, what Josh is saying is obviously completely valid and accurate (I changed my tune a little after reading the 3 articles you just posted ;-), in fact, I agree with most of what he has to say. As Josh himself says, multi-column keys result in more complex SQL.
In developing Cake, we've chosen to adhere to certain conventions in order to keep things simple. That's what makes Cake work. The decision not to allow the use of mutli-column primary keys is reflective of the opinions inherent to the framework. The rest of Josh's bullet points relate in one way or another to using something other than an auto-incrementing integer value for the primary key. There are many legitimate reasons to do this and I have never argued otherwise, and we have always done our best to support text-based and other types of numeric keys which are non-incrementing. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
