wrote a quick introduction
This commit is contained in:
parent
e9d096e411
commit
6cd778f940
@ -3,12 +3,14 @@ Persisting the Decorator Pattern
|
|||||||
|
|
||||||
.. sectionauthor:: Chris Woodford <chris.woodford@gmail.com>
|
.. sectionauthor:: Chris Woodford <chris.woodford@gmail.com>
|
||||||
|
|
||||||
INTRO
|
This recipe will show you a simple example of how you can use
|
||||||
|
Doctrine 2 to persist an implementaton of the
|
||||||
|
`Decorator Pattern <http://en.wikipedia.org/wiki/Decorator_pattern>`_
|
||||||
|
|
||||||
Component
|
Component
|
||||||
---------
|
---------
|
||||||
|
|
||||||
Since the ``Component`` class needs to be persisted, it's going to
|
The ``Component`` class needs to be persisted, so it's going to
|
||||||
be an ``Entity``. As the top of the inheritance hierarchy, it's going
|
be an ``Entity``. As the top of the inheritance hierarchy, it's going
|
||||||
to have to define the persistent inheritance. For this example, we
|
to have to define the persistent inheritance. For this example, we
|
||||||
will use Single Table Inheritance, but Class Table Inheritance
|
will use Single Table Inheritance, but Class Table Inheritance
|
||||||
|
Loading…
Reference in New Issue
Block a user