|
An application table, in the context of USoft Delivery Manager and in the context of an application, is each:
•database table or interface table, •defined for the application, •and made known * to Delivery Manager. * To make a database table or interface table known to Delivery Manager, you must run the Populate tables list action for the application and for the database account where you want to take the table definitions from. This requires that the application and the database account are first declared in Delivery Manager.
The purpose of having lists of Application Tables in Delivery Manager is that you can specify deliverable tables, skipped tables, and upgrade hints.
For each application table in Delivery Manager, you can specify that it is deliverable (choose Define, Application Tables, query the application table record, and set Deliverable = Yes for it).
Deliverable tables are "technical tables" that contain data that you want to deliver to Production and other target machines. You can automate this delivery by calling the Export deliverable appdata action. Click here for background information on deliverable metadata and application data.
|
For each application table in Delivery Manager, you can specify that it is to be skipped (choose Define, Application Tables, query the application table record, and set Skip = Yes for it).
Skipped tables are ignored when Delivery Manager is asked to generate a create-tables upgrade script. This allows you to write your own upgrade script for the skipped table (if necessary) and add it to the list of upgrade scripts for that release.
IMPORTANT: When you move to the next release by running the Create New Release routine, all Skip settings for all application tables are automatically undone. Accordingly, upgrade scripts are also automatically linked to the current release only: they do not automatically apply to the next release.
Skipped in previous release
The "Skipped in previous release" column shows the tables that you skipped in the previous release. If you decide to revert to that release (Revert button in Current Release window), those Skipped settings will be re-applied. This works only 1 level deep: Skipped settings for the previous release are remembered, but Skipped settings for all the earlier releases are forgotten.
|
For each application table in Delivery Manager, you can specify Upgrade Hint = "Create or Alter" (the default) or Upgrade Hint = Create. (Choose Define, Application Tables, query the application table record, and set Upgrade Hint for it).
Upgrade Hints are relevant when the structure of the physical table in the database changes in your current release and you ask Delivery Manager to generate a create-tables upgrade script.
•If Upgrade Hint = "Create or Alter", Delivery Manager will decide automatically whether an ALTER TABLE statement or a CREATE TABLE statement is generated. Generally, ALTER TABLE is given precedence unless there is a logical reason to fall back on a CREATE TABLE strategy. •If Upgrade Hint = "Create", CREATE TABLE is used. For more background, go to the Create-tables script help topic.
|
See also
Export deliverable appdata
Create-tables script
Populate tables list
Applications
|
