Well, the first one was quite interesting in the way it condemned the use of primary keys altogether. I think it's way off base, but still interesting.
The bottom line for me is that (a) it introduces needless complexity into the system, and (b) not only does the practice of using join table foriegn keys as composite primary keys smack of referential integrity badness, (c) it also confuses the purpose of the keys and introduces dangerous dependencies into the system. If the join record links to another record, you lose your reference to the original join record. This is not how you normalize a database. If your join table is doing anything besides representing links between other tables, it needs a universally unique, singular primary key. This elevates the domain model, actually making those records accessible units of data. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
