> > @Felix, yes you right for cake 1.2, sorry Nothing to be sorry about ; ). But why am I right for 1.2 only? I suggest using an id field join tables, even if it's not a PHP app ^^.
-- Felix -------------------------- My Blog: http://www.thinkingphp.org My Business: http://www.fg-webdesign.de francky06l wrote: > @Felix, yes you right for cake 1.2, sorry > > On Jul 19, 4:24 pm, Felix Geisendörfer <[EMAIL PROTECTED]> wrote: > >>> The primary key is the combination of the 2 fields. >>> >> Don't do that. Give it an id. It will make your life *much* easier. It >> will allow you to create a model for you join table and easily model >> relationships >> <http://www.thinkingphp.org/2006/10/26/modeling-relationships-in-cakep...>. >> >> Compound keys are never ever a good idea. I'm not saying it can't be >> done, but it will make your life harder. So please, add an 'id' column >> to your join table. >> >> -- Felix >> -------------------------- >> My Blog:http://www.thinkingphp.org >> My Business:http://www.fg-webdesign.de >> >> francky06l wrote: >> >>> The primary key is the combination of the 2 fields. >>> >>> On Jul 19, 3:54 pm, rtanz <[EMAIL PROTECTED]> wrote: >>> >>>> hi when i have a join table such as users_modules do i have to make a >>>> separate id for the table itself or will the primary key be the >>>> combined fields user_id and module_id? >>>> >>>> thanks >>>> > > > > > > --~--~---------~--~----~------------~-------~--~----~ 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?hl=en -~----------~----~----~----~------~----~------~--~---
