DBDesigner is great in some ways, but a real pain in others. For example, if you create a A hasMany B relationship, it creates a foreign key for you in B. That's fine. But it makes that foreign key part of a composite primary key for table B. Don't understand the reason for that.
The problem is if you have a B hasMany C relationship, it creates two foreign keys in table C, one for each part of the composite key in B. Another issue, if you ever have to delete a relationship because you accidentally input it in reverse and want to change it's direction, you could end up deleting the primary key in one of the tables. And the effect ripples to all other tables which may have foreign keys to that table. So, one small mistake can cause you lots of cleanup work. I wasn't happy about that aspect. It's enough to prevent me from using it with cake. A final question: how important are REAL foreign keys in the database, if you are using cake associations. Are they superfluous? Are they still needed? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
