PowerDesigner User Recommendation (Full Version)
1. PowerDesigner User Recommendation 1.2 Business Rule This is recommended to be in multiple data tables for some business logic, which is recommended to encapsulate business rule, so that the business logic is reused, it is also easy to maintain business. To facilitate maintenance of business logic, you can consider combining business rule and domains. Apply Business Business Rule to Domains and then apply Domains to the fields of the data table. For example, in the demolition project, the demolition business part, the management parameter business part, the listing of the list, and the data sheet in the demolition contract part has the floor, so a business rule, then define a Domain, thus corresponding data sheet This Domain can be used in the field. 1.2. Custom Data Types (Domains) use Oralce to provide some built-in data types, but users can define custom data types based on the needs of the business. Package business logic in the custom data type. As the home floor above, we can define a separate data type (Domain) maintenance, then use this custom data type on the field of the relevant data table. Generally defined in the Oracle's basic type of Oracle, you can add some Standard Check or Business Rules. For example: In the demolition item, the area category This field has appeared in many data tables, which can be maintained as a separate data type class, define a "area category" Domains (included: 0 --- House area, 1 --- Using the area, 2 --- unit area, 3 --- total building area, 4 --- distribution area). And due to the provision of PowerDesigner, so that it is easy to query those objects that are affected quickly when business logic changes. 1.3 Serial Number (Sequence) Use In PowerSigner's model, you define a pile of Sequence, which is the next thing to associate them with the relevant fields of the data table, especially those for multiple data table fields. One data sheet only allows a field to use Sequence, and before the field of the data table uses Sequence, you should add this Sequence to the extended DependenCies of the data table. If a data table has 2 fields or more fields that use Sequence, the model checks will give the prompt information. The rules used are typically only applied to the primary key field of the data table. Primary key field suggestion is data table "ID" or "numbered" configuration. For example: "House Integration Area" data table, the primary key field = housing integrated area number, the corresponding sequence is the SEQ_ housing integrated area. Other data sheets may also use this Sequence, which also needs to set a reference relationship before use. (Setting a reference relationship on the extended DependenCIES of the data table) 1.4 Oracle Package can set some procedure in Oracle Package, but what are the database objects referenced by the Oracle package, which is recommended to maintain it manually. In particular, Oracle Package uses which data sheets, views, and Oracle Packag and other information suggested. 1.5 Packages of PowerDesigner packages equivalent to folders. Users can treat it as a container that maintains business logic. The PowerDesigner package is generally recommended in accordance with the business module. If the module needs to be subdivided, consider establishing a PowerDesigner sub-package to complete. It is recommended to save the shortcut to the model object in the container. Original information is recommended not to put it in the container.
This way information may not be maintained because of the mode of the PowerDesigner's model, in the container, in the container. PHYSICALDIAGRAM below PowerDesigner is recommended to organize the object contained in a topic or business perspective as a topic or business perspective, so that each PhysicalDiaGram is clear. 1.6. Viewing views of views are typically established on a data sheet or view (of course, some stored procedure may also be referenced). The reference information of the data source of the view should be maintained in the model of the general view. In our current project, the database model does not maintain the view, which requires the PowerDesigner model for the view. I can't get the script by reverse engineering in the PowerDesigner9.5 environment, and cannot get the script by modifying the relevant configuration parameters. The script of the view (view) can be obtained by the following 2 method. Method 1: Use the reverse engineering of PowerDesigner 8.0 to obtain the view's script, then merge the view of the view in PowerDesigner9.5, so you can maintain the view. Method 2: Use erwin reverse engineering to get the Erwin model of the view, then save the model as an ERX type file to import the file in PowerDesigner9.5, then the merge model can be comparable to PowerDesigner's view model processing capability, unable to construct Maintaining the dependencies of the view (that is, establish a view of the data source on the data source), this is obviously worse than Erwin. 1.7. Synonym (Synym) The synonym is equivalent to an alias for database objects, providing the independence of location and data. When accessing an object across database users, you can consider establishing synonyms to combine permission assignments, simplifying database objects. 1.8. The update of the annotated statement of the data sheet. Business background: In our project, the annotated statement of the data table in the Erwin model is not synchronized to the Oracle database. Now you need a comment statement of a data table in a database. Implementation methods that may be taken: Method 1: Erwin directly forwards the project, but directly from Erwin is directly forwarded by the return symbol in the comment statement, the update will fail. Method 2: If the Erwin model is converted into the Note statement of the PowerDesigner model to update the data sheet, it can avoid the problem of the carriage return symbol, which is available in normal case, but due to the logic model and physical model in the erwin model. Inconsistent, even the order they appear inconsistent, so that the PowerDesigner model is incorrect, the buffer of the generated modified database is not correct. The method actually adopted: convert the ERWIN model into the PowerDesigner model Save as the ERX type in Erwin, and then save the file as a PDM type (XML format), delete the view in the model, Domains, Business Rule, Reference and other information, leaving only the information of the relevant data table itself, then modify the XML of the model file, and use XMLSPY to generate the DTD file of this file, and use Java to write a SAX-based program to parse the XML file, put each The note statement of the data sheet and field is extracted, then update the annotation statement of the data sheet and field in the database, so it is possible.
1.9. Erwin Upgrade to PowerDesigner Related Questions 1.9.1 Domain Upgrade Upgrade from Erwin 3.52 to PowerDesigner9.5, Domain Information and Data Table's association will be lost, need to manually re-add 2 relationships between 2 people. Of course, the model file of PowerDesigner can be modified by programming, and the association relationship between 2 is added. The general PowerDesigner model file is large, as long as there is a dozens of data sheets affirmation model files have 1MB, it is recommended to add information in SAX. Note: Time to add Domain used by the data table field, you need to set the data sheet to Domain's reference relationship (also extended Dependencies). 1.9.2 Business Rule Upgrade from Erwin 3.52 to PowerDesigner9.5, Business Rule's Expression (script) needs to be modified, modify the @Column in the expression of all business rules into a specific implementation of the% column% , You can modify directly in PowerDesigner9.5; or save the model as an XML format (file class .pdm), modify it through tools such as UltraEdit or Xmlspy, and a lookup is replaced. Of course, attention can only modify the contents of
