Versions Compared

Old Version 30

changes.mady.by.user Chandresh Patel

Saved on

compared with

New Version 31

changes.mady.by.user Karl Henselin

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Info

When renaming columns and tables in the same build, set the properties like:

FDORA_TABLE_RENAMES - schema.old_table = schema.new_table

FDORA_COLUMN_RENAMES - schema.old_table.old_column = schema.new_table.new_column


Since release 5.5.1, you can specify the renames without Schema prefixes, if you also leave the project property FDORA_SCHEMA_NAME blank. In this case, the schema will be set to the value of FDORA_USER and this value will be used for all renames.


FDORA_TABLE_RENAMES - old_table = new_table


FDORA_COLUMN_RENAMES - old_table.old_column = new_table.new_column




Environment/Instance Properties

...

Property Name

Property Code

Required

Description

Oracle Database Schema Name(s)FDORA_SCHEMA_NAME

Yes, until version 5.5.1.

Then it is not required.

Comma-separated list of schemas controlled by this project.

Typically this will be provided. However, since release 5.5.1, this property is optional.

If it isn't provided, FDORA_USER will be the schema that is tracked, and may differ through environments.


Inputs

Input Name

Input Code

Required

Description

Column Drop ActionFDORA_COL_DROP_ACTIONNo

Determines what action to take for "dropping" columns.

Can be set to SET UNUSED or DROP.

Defaults to SET UNUSED

Preview ExecutionFDORA_PREVIEW_EXECUTIONNo

Whether to bypass actual execution of the DDL, and simply run the compare.

Defaults to true.

For Pre-deploy workflow this should be checked to only run compare and generate report for review. In addition FDORA_OUT_CHANGES_EXIST output should be saved in FD_REVIEW_REQUIRED workflow output for Pre-deploy workflow and in addition FD_REVIEW_GROUP to assign Review tasks to specific group(s).

FDORA_ROLLBACK_ON_FAILNo

If a deployment failure occurs, should the database be rolled back to the previous state?

Defaults to false.

If true, the snapshot taken as the deployment starts will be rolled back to. If false, the database will be left in the state it is in after the first failure. The deployment stops after the first failure occurs.

FDORA_FAIL_AFTER_ROLLBACKNo

Added in 4.0.3.65.

If a deployment failure occurs, but it is successfully rolled back to the previous version, should the workflow still be failed?

Defaults to true.

...