| 1. | (Re-)checks all upgrade scripts (if any) that are associated with the current release version of "Application". |
| 2. | If Step 1. is successful, copies the scripts to the "scripts" subfolder of the current release folder. |
| 3. | If "Include physical tables upgrade script" = Yes, the Release create-tables script action is called as part of the routine. This causes the database upgrade script to be (re-)compiled and written to the \scripts folder. The database upgrade script is named "200.application.upg.rdbms.sql". |
| Data for this database upgrade script is read from the Database Account that is set as the "Source for Post-upgrade Check" property of "Application".
CAUTION: The set of tables included in the database upgrade script depends on the list of Application Tables in Delivery Manager with Skip = No (the default). But this list is not automatically brought up-to-date. To bring it up-to-date, you must call Populate tables list. See Release create-tables script for details. |
If you have previously released scripts for this version of this application other than the database upgrade script, they are overwritten.
If you have previously released the database upgrade script for this version of this application, and you now run with "Include physical tables upgrade script" = No, that database upgrade script is NOT overwritten.
When you call this action, if the current release has "Include attachments" = Yes, attachments for the "scripts" section (if any are defined) are copied to the specified subfolder of the "scripts" subfolder. This happens only to attachments that have Blocked = No (the default).
To release only the database upgrade script, run the "Release create-tables script" action instead.
Parameters
Name
|
Type
|
Optional?
|
Application
|
Application
|
No
|
Include physical tables upgrade script
|
Option flag
|
No
|
|
