To view or edit a view's properties, double-click its diagram symbol or Browser or list entry. The property sheet tabs and fields listed here are those available by default, before any customization of the interface by you or an administrator.
Property |
Description |
---|---|
Name/Code/Comment |
Identify the object. The name should clearly convey the object's purpose to non-technical users, while the code, which is used for generating code or scripts, may be abbreviated, and should not normally include spaces. You can optionally add a comment to provide more detailed information about the object. By default the code is generated from the name by applying the naming conventions specified in the model options. To decouple name-code synchronization, click to release the = button to the right of the Code field. |
Stereotype |
Extends the semantics of the object. You can enter a stereotype directly in this field, or add stereotypes to the list by specifying them in an extension file. |
Owner |
Specifies the name of view owner. You choose an owner from a list of users. A view can only have one owner at a time. This is normally the view creator. |
Usage |
Specifies the use of the view: Query only defines a view for consultation only, view cannot update tables; Updatable defines a view for consultation and update, view can update tables; and With Check options implements controls on view insertions. |
Dimensional type |
Specifies the type of the view for purposes of creating star or
snowflake schemas containing fact tables and dimensions.
PowerDesigner's support for BusinessObjects universes (see Generating a BusinessObjects Universe), will use this information if it
is available. You can choose between:
|
Type |
Specifies the type of the view, where supported by your DBMS. For information about DB2 and SQL Anywhere materialized views, see Materialized Views. For information about XML views, see Creating an XML Table or View. |
Generate |
Includes view generation as part of database generation script. |
User-defined |
When selected, makes sure the view query is not parsed by PowerDesigner internal parser. This protects the view query from any update using model objects and keeps its syntax as defined by user. Otherwise, the view query is parsed and modified according to model values. |
Keywords |
Provide a way of loosely grouping objects through tagging. To enter multiple keywords, separate them with commas. |
Columns - lists the columns in the view based on the SELECT orders from the queries. You can modify column properties in this list but to add or remove columns, you must modify the appropriate view query. View column properties are initialized from the properties of their source columns. The read-only Expression column specifies the qualified name of the view column.