When the Oracle flavor is chosen for database top level element (schema or database), additional Oracle extensions are brought in. Elements that are in the scope of this schema or database element obtain additional Oracle-specific properties in the Specification windows (under the separate Oracle property group). These properties carry an additional information, that is then used when generating DDL scripts for Oracle.
Most often there is just one Additional Properties property - allowing entering free-form text that is then used when generating (this can be used to specify any extension texts - such as tablespace options for tables).
Oracle extensions provide means to model synonyms. Synonym is mapped as follows.
- Element of the same type (that is, table, materialized view, stored procedure, sequence) as the one being aliased is created. It is stereotyped as appropriate, but have no other data - just its name is important.
- Additionally, stereotype «OraSynonym» will be applied on the element. It has ref:Element[1] tag for pointing to the element being aliased. Synonyms of synonyms are handled in the same way.
Oracle extensions provide means to model materialized views. Materialized view can be created from Oracle SQL diagram. It is an ordinary SQL view, but with the additional «OraMaterializedView» stereotype applied (in diagrams, a shortened keyword «materialized» is used for the sake of compactness).