Templates provide the ability to customize automatically generated code within RED. This feature is most suited to users that would like to customize automatically generated code or would like to expand RED to support non-native database platforms.

Creating templates is an advanced function that requires intimate knowledge of RED operations and metadata structure. WhereScape recommends that you contact our consulting team to assist with this feature. However, should you wish to use this feature independently, example templates and up-to-date reference information is available on our website:

https://www1.wherescape.com/support/software-downloads-documentation/enablement-packs/

Each template is assigned a type and a target database, these properties are used to assist with filtering when associating table operations to templates. RED supports templates for the following operations:

Operation

Database

Template Type

Alter Table DDL

Custom (on SQL Server)

DDL

Create Table DDL

All database types

DDL

Create Index DDL

Custom (on SQL Server)

DDL

Drop Index DDL

Custom (on SQL Server)

DDL

Export Script

All database types

Windows Script



PowerShell Script



Unix Script

Load Script

All database types

Windows Script



PowerShell Script



Unix Script

Update Procedure    

Custom (on SQL Server)

Block



PowerShell Script


Hive

Block


SQL Server and PDW

Block



Procedure

Custom Update Procedure

SQL Server

Procedure

Update Script

Custom (on SQL Server)

PowerShell Script

Post Load Procedure

Custom (on SQL Server)

Block


Hive

Block


SQL Server and PDW

Block


SQL Server

Procedure

Post Load Script

Custom (on SQL Server)

PowerShell Script

Utility-type templates contain common code for use by other templates.
Templates are written in the Pebble template language—refer to Pebble Templates and Pebble Syntax sections for details.
You can also define default templates to use for the update routines of table objects in RED by Connection type—refer to Connection Routine Templates for details.

Detailed logs can be produced during template evaluation by typing FULLLOG in the Notes of the relevant connection.

  • No labels