Procedure
- Review the STAGLOG table
information. Use the STAGLOG table information and this topic to create
the required triggers for the custom table.
- Gather the following information about the custom table:
- table name
- table scope (site, merchant, or mixed site and merchant)
- primary or unique key columns
Rows in staging-enabled tables
rows must be uniquely identifiable by at most five columns: Two columns
containing strings (maximum length: 254 characters) and three columns
containing numbers (maximum length: BIGINT). If your custom table
does not have uniquely identifiable rows within these restrictions,
modify your custom database table to meet these criteria.
- Put SQL statements to create three triggers for the custom
database table in the wcs.stage.trigger.sql file.
You must create three triggers:
- An INSERT trigger to capture insert operations on the custom table.
- An UPDATE trigger to capture update operation on the custom table.
- A DELETE trigger to capture delete operations on the custom table.
- Ensure that your triggers follow all rules for creating triggers for
custom tables.
- Manually run the wcs.stage.trigger.sql script
file to generate the triggers on the relevant table.
Note: To verify the triggers defined, you run the following SQL statements
to query the system table
ALL_TRIGGERS
:
select * from all_triggers;
- Put SQL statements to drop the three triggers in the wcs.droptrigger.sql
file.