Hi list, I'm a bit confused with doctrine "generated classes" for OM (BaseXXX.class.php).
I'm trying to figure when to use hasOne or ownsOne, but the generated classes seem to always use hasOne or hasMany but never ownsOne/ ownsMany. What I understand from doctrine documentation is that one has to use "hasOne" when the foreign key is in the related model and "ownsOne" when the foreign key is in the current model. (see for instance http://doctrine.pengus.net/doctrine/manual/documentation2.php?chapter=Object+relational+mapping+-+Relations+-+Foreign+key+associations+-+One-to-One) Yet, the logic seems to be inverted with hasMany/ownsMany. cf : http://doctrine.pengus.net/doctrine/manual/documentation2.php?chapter=Object+relational+mapping+-+Relations+-+Foreign+key+associations+-+One-to-Many%2C+Many-to-One Anyway, I think doctrine documentation needs to be more precise if it is supposed to become a strong alternative choice to Propel. F. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
