I'm not sure that a lot of people really understand what's going on behind the scenes here.
You are writing code .... that writes code..... Some things are simply more practical. You need certain conventions or there would be a gazillion configurations that need to be set before you can start. Sorry for the rant. I'm not even on the team On Feb 7, 2008 6:29 AM, RichardAtHome <[EMAIL PROTECTED]> wrote: > > I doubt the naming of any keys would have any effect on database > performance. > > CakePHP is flexible enough to allow you to use any primary key name in > your tables, but if you use the recommended format you will find that > cake does a lot more automatically. > > See Model::primaryKey ( > http://api.cakephp.org/1.2/class_model.html#19ba09de3c283f574a175db48a6acab4 > ) > > On Feb 7, 11:04 am, Guillaume Chomat <[EMAIL PROTECTED]> > wrote: > > Hi everyone, > > > > I'm little newby in cake so perhaps it would be simple to answer to my > > concerns. > > According to my knowledge a natural join is better when the two joined > > fields have the same name. > > In the cake policy the primary key and referenced one have different > > name: 'id' and '<table>_id. > > Is the performance issue minor in join queries? What the initial > > reason to chooce this policy? > > > > Best regards. > > > > PS: Thanks for the cake team for this very great job. I hope to be > > able to participate for the evolution of our framework in 2008. > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
