Page History

This section reviews Cameo Data Modeler support for DDL script flavors from different vendors.

Standard SQL2

For SQL2 statements supported by Cameo Data Modeler, see see Supported SQL statements.

The MagicDraw UML schema package is located within a database package. The database definition statement is not part of the SQL2 standard; it is an analogue of a Database (a Catalog).

Oracle

Cameo Data Modeler Oracle DDL script generation is based on the Velocity engine. This enables you to change a generated DDL script by changing the velocity template. In this chapter we introduce how Oracle DDL generation works in MagicDraw and how to change a template for specific things.

It is necessary to understand the Velocity Template Language to edit or create templates. You can download the Velocity documentation from http://click.apache.org/docs/velocity/VelocityUsersGuide.pdf.

For more information about Oracle DDL generation and customization, see see Oracle DDL generation and customization in  in the MagicDraw User Guide.

Oracle dialect

For more information about Oracle DDL 11g, see http://download.oracle.com/docs/cd/B28359_01/server.111/b28286/toc.htm.

The Oracle dialect has CREATE DATABASE, CREATE INDEX, and CREATE TRIGGER statements that are not part of SQL2 standard but are taken into account while reversing the DDL script of this dialect.

This dialect has some syntax differences from SQL2 standard because of extensions (e.g. some schema definition statements can have STORAGE clause). These extensions are ignored while reversing.

Code engineering features for Oracle dialect are more extensive than code engineering for other dialects. In addition to the concepts supported by Standard SQL generation, Oracle generation supports the generation and reverse of the following items:

• Sequences
• Synonym
• Structured user-defined types (with methods, map & order functions)
• Function and procedure
• Users, roles grants
• Materialized views

Cloudscape

Informix Cloudscape v3.5 dialect has no database definition statement. It uses a database package with the name specified by the CurrentDatabaseName property.

This dialect has CREATE INDEX and CREATE TRIGGER statements that are not part of a SQL2 standard but should be taken into account while reversing the DDL script of this dialect. This dialect has some syntax differences from SQL2 standard because of extensions (e.g. some schema definition statements can have a PROPERTIES clause). These extensions are ignored while reversing.

Related page