You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cayenne.apache.org by aa...@apache.org on 2010/08/04 18:41:08 UTC
svn commit: r982324 - in
/cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler
Guide/Modeling Object Layer: Inheritance overview/ Modeling Inheritance/
Modeling Inheritance/Modeling Single Table Inheritance/ Modeling I...
Author: aadamchik
Date: Wed Aug 4 16:41:07 2010
New Revision: 982324
URL: http://svn.apache.org/viewvc?rev=982324&view=rev
Log:
refreshing docs
Removed:
cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler Guide/Modeling Object Layer/Inheritance overview/index.html
cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler Guide/Modeling Object Layer/Inheritance overview/inheritance-example.png
cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler Guide/Modeling Object Layer/Inheritance overview/inheritance-overview.png
cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler Guide/Modeling Object Layer/Modeling Inheritance/inheritance-diagram.jpg
Modified:
cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler Guide/Modeling Object Layer/Modeling Inheritance/Modeling Single Table Inheritance/index.html
cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler Guide/Modeling Object Layer/Modeling Inheritance/Modeling Vertical Inheritance/index.html
Modified: cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler Guide/Modeling Object Layer/Modeling Inheritance/Modeling Single Table Inheritance/index.html
URL: http://svn.apache.org/viewvc/cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler%20Guide/Modeling%20Object%20Layer/Modeling%20Inheritance/Modeling%20Single%20Table%20Inheritance/index.html?rev=982324&r1=982323&r2=982324&view=diff
==============================================================================
--- cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler Guide/Modeling Object Layer/Modeling Inheritance/Modeling Single Table Inheritance/index.html (original)
+++ cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler Guide/Modeling Object Layer/Modeling Inheritance/Modeling Single Table Inheritance/index.html Wed Aug 4 16:41:07 2010
@@ -62,13 +62,13 @@
<p>Let's look at a specific example shown below. An online bookstore may be selling regular paper books and electronic books. Both share a number of common attributes placed in a common superclass "Book", but also have a number of specific attributes found only in each book distribution format:</p>
-<p><span class="image-wrap" style=""><img src="single-table-inheritance.png?version=1&modificationDate=1280228715730" style="border: 0px solid black" /></span></p>
+<p><span class="image-wrap" style=""><img src="single-table-inheritance.png?version=1&modificationDate=1280228715000" style="border: 0px solid black" /></span></p>
<blockquote><p>As with many other ORM inheritance examples, this one is contrived and oversimplified. In a real bookstore it is likely that the same book is available in both formats, so mapping this inheritance hierarchy as a composition may be more appropriate, but let's stick with this example for simplicity sake.</p></blockquote>
<p>As you see, a "BOOK" table contains attributes from superclass and all subclasses, plus it has the ID (primary key) and a "TYPE" column which will be used as a "discriminator colum" to determine which sublcass is stored in each row. Mapping of this inheritance hierarchy, just like mapping a single class, starts by creating a DbEntity for the "BOOK" table:</p>
-<p><span class="image-wrap" style=""><img src="book-dbentity.png?version=1&modificationDate=1280229286128" style="border: 0px solid black" /></span></p>
+<p><span class="image-wrap" style=""><img src="book-dbentity.png?version=1&modificationDate=1280229286000" style="border: 0px solid black" /></span></p>
<p>Now let's create a superclass "Book", mapping only the columns that should be in the superclass (you can do it by clicking on "Create ObjEntity" icon on the DbEntity toolbar, and then removing unneeded subclass attributes). The next step is to create two subclasses. For each one of them, create a new ObjEntity, then under "Inheritance" dropdown specify "Book" as a superclass. This automatically selects "Table/View" to be "BOOK". </p>
@@ -80,7 +80,7 @@
</ul>
-<p><span class="image-wrap" style=""><img src="book-qualifier.png?version=1&modificationDate=1280230324133" style="border: 0px solid black" /></span></p>
+<p><span class="image-wrap" style=""><img src="book-qualifier.png?version=1&modificationDate=1280230324000" style="border: 0px solid black" /></span></p>
<blockquote><p>Unlike some other ORMs, Cayenne is really flexible about the semantics of discriminator columns. Qualifier can be any valid Cayenne expression, as long as it doesn't span any relationships (i.e. uses columns of the root table only). It doesn't have to be a single collumn, it can contain less or greater expressions. E.g. "<tt>price > 500</tt>", "<tt>type = 'E' and sizeMB < 1000</tt>", etc. Note however that if the expression is not settable (e.g. when using < or >), Cayenne won't be able to guess the right values on insert and the user application must provide those values explicitly. </p></blockquote>
Modified: cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler Guide/Modeling Object Layer/Modeling Inheritance/Modeling Vertical Inheritance/index.html
URL: http://svn.apache.org/viewvc/cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler%20Guide/Modeling%20Object%20Layer/Modeling%20Inheritance/Modeling%20Vertical%20Inheritance/index.html?rev=982324&r1=982323&r2=982324&view=diff
==============================================================================
--- cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler Guide/Modeling Object Layer/Modeling Inheritance/Modeling Vertical Inheritance/index.html (original)
+++ cayenne/main/branches/STABLE-3.0/docs/doc/src/main/resources/doc/Documentation/Modeler Guide/Modeling Object Layer/Modeling Inheritance/Modeling Vertical Inheritance/index.html Wed Aug 4 16:41:07 2010
@@ -62,7 +62,7 @@
<p>Continuing with the example used for <a href="../../../../../Documentation/Modeler Guide/Modeling Object Layer/Modeling Inheritance/Modeling Single Table Inheritance/index.html" title="Modeling Single Table Inheritance">single table mapping</a>, let's re-map it as vertical inheritance.</p>
-<p><span class="image-wrap" style=""><img src="vertical-inheritance.png?version=1&modificationDate=1280230992379" style="border: 0px solid black" /></span></p>
+<p><span class="image-wrap" style=""><img src="vertical-inheritance.png?version=1&modificationDate=1280230992000" style="border: 0px solid black" /></span></p>
<p>Note that in Cayenne <b>vertical</b> is essentially <b>single table with flattened attributes in subclasses</b>. We'll demonstrate this below.</p>
@@ -70,7 +70,7 @@
<p>On the ObjEntity end, there is no difference in mapping qualifier (it is needed), superclass, root table ("Table/View" for subclasses is still "BOOK"). The only difference is that subclass-specific attributes are mapped as "flattened attributes":</p>
-<p><span class="image-wrap" style=""><img src="flattened_attribute.png?version=1&modificationDate=1280231422730" style="border: 0px solid black" /></span></p>
+<p><span class="image-wrap" style=""><img src="flattened_attribute.png?version=1&modificationDate=1280231422000" style="border: 0px solid black" /></span></p>
<blockquote><p>Note that flattened attributes can be used with or without inheritance, however in combination with single-table inheritance mapping, they give us "vertical" inheritance.</p></blockquote></div>
</div>