I think a autoincrement unique id is just slowing things down here.
We always query multiple rows based on duplicate entries.
In other words: We dont ask for "id" 1 to 20 in the joinTable, we ask for "post_id" number 5 (which may have many unique "comment_id".)
In a HABTM within the post-model i would put INDEX on post_id. On the other end (comments) it is a belongsTo-situation anyways.
What you think?
2006/9/25, nate <
[EMAIL PROTECTED]>:
It's always best to have. It makes for faster indexing, and CakePHP
does not currently, nor will it ever, support composite primary keys.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
- Re: table relations nate
- Re: table relations Matt Adams
- Re: table relations nate
- Re: table relations Kjell Bublitz
