It seems the picture in thte post before did not work, here is a link: *My Object Structure should look as follows: * https://www.dropbox.com/s/otxrm4eiw8c8wzy/ausschnitt_doctrine_forum_2.png
Am Montag, 2. Juni 2014 13:34:11 UTC+2 schrieb Ulrich Lichtenegger: > > Hi, > > I am searching for an inheritance strategy for the following problem. I > will describe my database and object structure and I would like to know if > its possible to map those. > > My Object Structure should look as follows: > > > > My Database structure looks like so: > > - *Application *(id, description, validfrom, validto, > application_only_attributes) > - *Organization* (id, description, validfrom, validto, > organization_only_attributes) > - *Organization_has_Application* (id, entity1, entity2, validfrom, > validto) <<-- A special version of a connection, it should inherit from > "connection" > > > So,* BaseEntity has no own table*. This is because otherwise nearly all > Entities of my Database would have an entry in BaseEntity - which does not > feel correct -> or am I wrong? > > On application-side, I would like to work with the interitance strategy. > Mainly because the entities are a graph - and I would like to easily > implement a function "graph walk" which can use the connection to go from > one child to another. > > > Is it possible to specify a mapping for inherited attributes in the child > classes in doctrine? Or which mapping strategy would you choose? > Thank you for your help! > > > > > > -- 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 http://groups.google.com/group/doctrine-user. For more options, visit https://groups.google.com/d/optout.
