Ben From an academic standpoint [and yes best practice DB design] the us of composite FKs to create a PK is common.
Many of my designs in the past used that idea, but with the introduction of so many QaD [Quick and Dirty] methods [aka Rapid Application Development] sometimes the best practices get left behind to form less than perfect solutions that *may be* more efficient when it comes to application development in short time. I know I'd prefer to refer to a composite/joint key such as [book_id, author_id] in a one-many-one table situation as then I know JOINS will result faster as the PK is always indexed. I am sure that cakePHP has some way to get around this hiccup... what I am not sure... Ady --- Adrian Gould Lecturer in IT / Network Engineering / Multimedia Business Finance & Computing [Midland Campus] Swan TAFE PO BOX 1336, Midland WA 6936 Phone: (08) 9267 7777 eMail: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
