#1515: Single Table inheritance is very restrictive. Joined Table Inheritance is
needed.
-------------------------------------------------------+--------------------
Reporter: Chekote | Owner: romanb
Type: enhancement | Status: new
Priority: critical | Milestone:
Component: Inheritance | Version: 1.0.2
Keywords: Joined Aggregation Inheritance Constraint | Has_test: 0
Mystatus: Pending Core Response | Has_patch: 0
-------------------------------------------------------+--------------------
Single table inheritance has many flaws which are preventing my projects
from being implemented in Doctrine. The main one being failed constraints
on unrelated objects. For example:
There are three classes: A, B and C. Both B and C extend A.
B has a property called "myProperty" that is not null.
Since both B and C exists within the same table, it is not possible to
persist instances of C without specifying the value of "myProperty", which
obviously is impossible because "myProperty" is a property of B, not C.
If Doctrine were to implement joined table inheritance; the properties and
constraints of B would have no affect on C, just as it should be.
I am not familiar with the Doctrine test suite yet, so my apologies at the
lack of a test case.
--
Ticket URL: <http://trac.phpdoctrine.org/ticket/1515>
Doctrine <http://www.phpdoctrine.org>
PHP Doctrine Object Relational Mapper
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"doctrine-svn" 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.co.uk/group/doctrine-svn?hl=en-GB
-~----------~----~----~----~------~----~------~--~---
