Developer Database Reminders

The following are important to remember when you are licensed to do development with this software:

• If you create a rendered class on the database, and subsequently change and render the class again in Oware, then you must implement the changes to the class on the database too. This could mean adding or recreating a table in the database. If business data already exists in the database table, exercise caution when implementing changes. These types of changes should be handled by an experienced database administrator.

• Four files run to create the database objects for the class (and they must be run in this order). Log in to your database utility as user oware (password default: dorado) to run the sql below.

1. The first script creates the table. It is in the format <packagename_classname_#>.sql. The # represents the level of inheritance starting at 0.

2. The second script creates the database triggers for the class. It is in the format create_<packagename_classname>_trigger.sql. Here is an example:

Package: MyCompany

Class: MyClass

Trigger Script: create_mycompany_myclass_trigger.sql

 

3. The third file script creates the database packages for the class. It is in the format cr_<packagename_classname>_pk.sql. Here is an example:

Package: MyCompany

Class: MyClass

Package Script: cr_mycompany_myclass_pk.sql

 

4. The fourth script inserts a row into an Oware Base table for the class. It is in the format create_<packagename_class­name>_class­table­­map.sql. Here is an example:

Package: MyCompany

Class: MyClass

Class Table Map Script:

create_mycompany_myclass_classtablemap.sql