Why on earth would you have composite keys in your database tables? There is absolutely no reason from them.
And Tony Marston is the last person I would be reading for advice on how to do anything related to application development, aside from the point he has been developing 1st 2nd 3rd 4th 5th and so on generation applications and make sure to mention it in every post he has ever commented on in numerous forums. His advice and techniques have been ridiculed to death so I would remove that URL from your book marks
Take that from the Cake Master himself, Composite keys are insane and not needed!
--
/**
* @author Larry E. Masters
* @var string $userName
* @param string $realName
* @returns string aka PhpNut
* @access public
*/
On 7/18/06, Sonic Baker <[EMAIL PROTECTED]> wrote:
I'm also concerned about having to use an 'id' field as a primary key to every table. Now bare in mind that I am just a mere mortal and cower in the shadows of the real cakePHP masters but I have beef with that fact that I can't have a primary key which consists of more than one field. However, this is the only real beef I have with cake and apart from this I think cake is the new "Sliced Bread".
Here's an article which played a big part in my concerns about having an 'id' field in every table:
http://www.tonymarston.net/php-mysql/technicalkeys.html
If you have a read of the above and tell me why it's not a concern then I'd be very open to taking my beef out of the equation and becoming a cakePHP vegetarian.
Cheers,
Psychie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Cake PHP" group.
To post to this group, send email to cake-php@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at http://groups.google.com/group/cake-php
-~----------~----~----~----~------~----~------~--~---
