Changes for page The EOModel

Last modified by Pascal Robert on 2012/03/10 15:42

From 32.1 to 33.1 From 36.1 to 37.1

From version 33.1

edited by Pascal Robert
on 2012/03/10 15:40

Change comment: There is no comment for this version

To version 36.1

edited by Pascal Robert
on 2012/03/10 08:28

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -247,11 +247,11 @@
  You can set up an EOModel so that Enterprise Objects automatically invokes a stored procedure for these operations on an entity:
--**Insert** to insert a new object into an entity
--**Delete** to delete an object from an entity
--**Fetch All** to fetch all objects in an entity
--**Fetch w/ PK** to fetch the object in an entity with a particular primary key
--**Get PK** to generate a new primary key for an entity
++Insert to insert a new object into an entity
++Delete to delete an object from an entity
++Fetch All to fetch all objects in an entity
++Fetch w/ PKto fetch the object in an entity with a particular primary key
++Get PK to generate a new primary key for an entity
  The stored procedures you enter in the Stored Procedure Inspector must correspond to a stored procedure in the model. If you created the model from an existing data source and chose the Ask About Stored Procedures option in the wizard, stored procedures are already added to the model. If this is not the case, however, you can add stored procedures to the model using the Add Stored Procedure command from the Property menu.
@@ -261,21 +261,21 @@
  For each of the operations, if the stored procedure associated with an operation returns a value, Enterprise Objects ignores the return value.
--For **Fetch All** operations, the stored procedure must not take any arguments and it should return a result set for all the objects in the corresponding entity. The rows in the result set must contain values for all the columns Enterprise Objects would fetch if it were not using the stored procedure, and it must return them in alphabetical order.
++For Fetch All operations, the stored procedure must not take any arguments and it should return a result set for all the objects in the corresponding entity. The rows in the result set must contain values for all the columns Enterprise Objects would fetch if it were not using the stored procedure, and it must return them in alphabetical order.
  That is, the stored procedure should return values for primary keys, foreign keys used in class property joins, class properties, and attributes used for locking. These values must be returned in alphabetical order with regard to the attributes with which they are associated. For example, consider a Listing entity that has the attributes listingID, bedrooms, and sellingPrice. A stored procedure that fetches all the Listing objects should return the value for a listing's number of bedrooms, then its listingID, and then its selling price.
--For **Fetch w/ PK** operations, the stored procedure must take an "in" argument for each of the entity's primary key attributes (most entities have a single primary key attribute). The argument names must match the names of the entity's primary key attributes. For example, a Listing entity has a single primary key attribute named listingID, so the stored procedures argument as defined in the model must also be listingID.
++For Fetch w/ PK operations, the stored procedure must take an "in" argument for each of the entity's primary key attributes (most entities have a single primary key attribute). The argument names must match the names of the entity's primary key attributes. For example, a Listing entity has a single primary key attribute named listingID, so the stored procedures argument as defined in the model must also be listingID.
--A **Fetch w/ PK** operation stored procedure should return a result set containing the row that matches the primary key passed in by the argument. The row must be in the same form as rows returned by the Fetch All operation.
++A Fetch w/ PK operation stored procedure should return a result set containing the row that matches the primary key passed in by the argument. The row must be in the same form as rows returned by the Fetch All operation.
--For **Insert** operations, the stored procedure must take an "in" argument for each of the corresponding entity's attributes. The argument names must match the names of the corresponding EOAttribute objects.
++For Insert operations, the stored procedure must take an "in" argument for each of the corresponding entity's attributes. The argument names must match the names of the corresponding EOAttribute objects.
--For **Delete** operations, the stored procedure must take an "in" argument for each of the entity's primary key attributes. The argument names must match the names of the primary key attributes as in a Fetch w/ PK operation stored procedure.
++For Delete operations, the stored procedure must take an "in" argument for each of the entity's primary key attributes. The argument names must match the names of the primary key attributes as in a Fetch w/ PK operation stored procedure.
--For **Get PK** operations, the stored procedure must take an "out" argument for each of the entity's primary key attributes. The argument names must match the names of the primary key attributes as in a Fetch w/ PK operation stored procedure.
++For Get PK operations, the stored procedure must take an "out" argument for each of the entity's primary key attributes. The argument names must match the names of the primary key attributes as in a Fetch w/ PK operation stored procedure.
--**Insert**, **Delete**, and **Get PK** operations should not return a result set.
++Insert, Delete, and Get PK operations should not return a result set.
  == EO Inheritance ==
@@ -347,53 +347,10 @@
  == EOGenerator ==
--For many years, a tool called **EOGenerator** was used by many developers to use the Generation Gap Pattern on the Enterprise Objects. Since **EOGenerator** was using a ObjectiveC <-> Java that Apple killed in Mac OS X 10.5, a 100% Java tool, **Veogen**, was added to WOLips, so by default everyone is now using it.
--
--By using **Veogen**, when you create a new EO entity in your data model, two Java class will be generated, one called //EntityName.java, and the other EntityName.java. The class starting with the underscore will be regenerated every time you modify the entity in the model, if you want to change something in that class, you need to change the template. The class without the underscore is the place where you can add other variables or methods.//
--
  == Handling Blob Data ==
  == Connection Dictionary ==
--In each EOModel, you can store one or many database configurations. A database configuration consists of the prototype selection for your database (MySQL, H2, etc.), the adaptor (99% of the time, it's JDBC), the URL (JDBC connection string), the username and password to connect to the datastore, the driver (JDBC driver name) and the name of the EOAdaptor plugin. You need to have at least one database configuration in your model so that you can use database migrations and reverse engineer a database to a model.
--
--When you launch your application, it will use the default database configuration from the model. An alternative to database configuration is to use properties in the Properties file to specify the connection dictionary. For example, for a H2 database, you can use a configuration like this:
--
--{{panel}}
--
--dbConnectUserGLOBAL=
--dbConnectPasswordGLOBAL=
--dbConnectURLGLOBAL = jdbc:h2:file:~/politimo
--dbConnectPluginGLOBAL = H2PlugIn
--
--{{/panel}}
--
--Using the **GLOBAL** properties will apply the properties to all models in your application (and to models in your frameworks). You can also specify propertiers per model, with those properties:
--
--{{panel}}
--
--\[MODEL_NAME\].DBDriver
--\[MODEL_NAME\].DBHostName
--\[MODEL_NAME\].DBPassword
--\[MODEL_NAME\].DBPlugin
--\[MODEL_NAME\].DBURL
--\[MODEL_NAME\].DBUser
--
--{{/panel}}
--
--So if your EOModel is called **Politimo**, the properties will be:
--
--{{panel}}
--
--\[Politimo\].DBDriver
--\[Politimo\].DBHostName
--\[Politimo\].DBPassword
--\[Politimo\].DBPlugin
--\[Politimo\].DBURL
--\[Politimo\].DBUser
--
--{{/panel}}
--
  == Runtime Selection of the Connection Dictionary and Prototypes ==
  == Debugging JDBC Connections and Jdbc2info ==

Changes for page The EOModel

Summary

Details

Applications

Navigation

My Recent Modifications

Need help?