Consultor Eletrônico

Status: Unverified

GOAL:

Using Multiple sets of r-code & -trig for DB Schema Triggers

GOAL:

This solution describes one way to implement database schema triggers for more than one database with the same table names.

SYMPTOM(s):

Table <table> is in database <db name> and <db name> (425)

CAUSE:

You are developing database schema triggers that are not pre-compiled and are intended to be used for the same tables in more than one database.

FIX:

You need to have separate r-code for each database that
will need the schema triggers. The -trig parameter can
then be used for each database to point to the appropriate
trigger code that has been compiled for that database.

So you essentially have one set of source code for the
database schema triggers and one set of r-code for each
database that uses those triggers.