To follow up on my last question.. and if you like a challenge, here is something I've designed and now trying to implement in Doctrine:
http://stackoverflow.com/questions/39397170/how-do-i-model-my-er-diagram-when-doctrine-wont-let-me-associate-composite-fore I have made category_pricename relation to be its own Entity. And I've done the same with product_pricename. I seemed to have been able to transfer the ER Diagram amicably into Doctrine, by 1) making tables that held M:M relations into Entities 2) assigning surrogate primary keys to all tables/Entities/Relations - instead of trying to map composite primary keys onto foreign keys (Doctrine did not like). I was curious to see if there is a more official Doctrine stance on if the above is the right approach. Dennis -- You received this message because you are subscribed to the Google Groups "doctrine-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
