Changes for page The EOModel

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,9 +7,3 @@
1		-{{info}}
2		-
3		-Work in progress! Right now, most of the text is coming from Apple's documentation. We need to change that, and add Wonder and WOLips specific information.
4		-
5		-{{/info}}
6		-
7	7	{{toc}}{{/toc}}
8	8
9	9	= The EOModel =
...	...	@@ -31,7 +31,7 @@
31	31	■ define derived attributes
32	32	■ build database queries in raw SQL
33	33
34		-In an Entity-Relationship model, distinguishable things are known as entities, each entity is defined by its component attributes, and the affiliations, or relationships between entities, are identified (together, attributes and relationships are known as properties). From these three simple modeling objects~-~-entities, attributes, and relationships~-~-arbitrarily complex systems can be modeled.
	28	+In an Entity-Relationship model, distinguishable things are known as entities, each entity is defined by its component attributes, and the affiliations, or relationships between entities, are identified (together, attributes and relationships are known as properties). From these three simple modeling objects~-~--entities, attributes, and relationships~-~--arbitrarily complex systems can be modeled.
35	35
36	36	== Entities ==
37	37
...	...	@@ -120,7 +120,7 @@
120	120	~1. An entity named EOAdaptorNamePrototypes, where AdaptorName is the name of the adaptor for your model. WebObjects 5.2 includes an adaptor for JDBC data sources and an adaptor for JNDI data sources. So you can create a prototype entity called either EOJDBCPrototypes or EOJNDIPrototypes, depending on the adaptor you use.
121	121	2. An entity named EOPrototypes.
122	122
123		-To create a prototype attribute, first create a prototype entity~-~-an entity named either EOAdaptorNamePrototypes or EOPrototypes~-~-and add an attribute to it. Figure 3-3 shows an attribute in a prototype entity. It shows all the values that prototype attributes can define: column name, value class, external type, and value type.
	117	+To create a prototype attribute, first create a prototype entity~-~--an entity named either EOAdaptorNamePrototypes or EOPrototypes~-~--and add an attribute to it. Figure 3-3 shows an attribute in a prototype entity. It shows all the values that prototype attributes can define: column name, value class, external type, and value type.
124	124
125	125	To assign a prototype attribute to an attribute, reveal the Prototype column in table mode, and select a prototype attribute from the pop-up menu. The prototype attributes that appear in the pop-up list in the Prototype column include prototype attributes defined in any entity in any model in the application's model group, which includes the current model.
126	126
...	...	@@ -279,7 +279,7 @@
279	279
280	280	== EO Inheritance ==
281	281
282		-One of the issues that may arise in designing your enterprise objects~-~-whether you're creating a schema from scratch or working with an existing database schema~-~-is the modeling of inheritance relationships.
	276	+One of the issues that may arise in designing your enterprise objects~-~--whether you're creating a schema from scratch or working with an existing database schema~-~--is the modeling of inheritance relationships.
283	283
284	284	In object-oriented programming, it's natural to think of data in terms of inheritance. A Customer object, for example, naturally inherits certain characteristics from a Person object, such as name, address, and phone number. In inheritance hierarchies, the parent object or superclass is usually rather generic so that less generic subclasses of a related type can easily be added. So, in addition to the Customer object, a Client object also naturally derives from a Person object.
285	285
...	...	@@ -341,10 +341,6 @@
341	341
342	342	Single-table mapping results in tables that have columns for all of the attributes of each entity in the inheritance hierarchy. It also results in many null row values. While these aren't really disadvantages, they may conflict with some database design philosophies.
343	343
344		-=== Using Inheritance in Entity Modeler ===
345		-
346		-To use Inheritance in your model, you first need to create your base entity. When done, right-click on the entity and select Subclass. A dialog will appear and will ask you to specify which kind of Inheritance you want to use, which entity is the parent and the name of the new (child) entity. When selecting Vertical or Single-Table Inheritance, you can also specify the qualifier (type = XX) in that dialog (you can do that part later too).
347		-
348	348	== EOGenerator ==
349	349
350	350	== Handling Blob Data ==