-
Notifications
You must be signed in to change notification settings - Fork 3
Excluding Fields From Replication
If there are fields in a replicated record that you do not wish to include as columns in the database then you can mark those fields to be excluded from processing by adding the special text REPLICATOR_EXCLUDE in the fields user-defined text or long description in the repository, and then re-generating the code. Note that this special token is case sensitive, it must be declared exactly as shown, in upper case.
There are several reasons to exclude fields from replication, including but not limited to:
- Excluding sensitive or unreadable information from the database.
- Improving the performance of the replication environment (fewer columns results in improved performance).
IMPORTANT: It is not possible to exclude any field that is used as a segment in any access key. Attempting to do so will cause warning messages to be output to the generated code, which will in turn cause the code to fail to compile. These warning messages appear at the top of the generated source file and look like this:
*****************************************************************************
CODE GENERATION EXCEPTIONS:
Field EMP_ADDRESS_STATE may not be excluded via REPLICATOR_EXCLUDE because it is a key segment!
- Introduction
- Getting Started
- Downloading the Code
- Setting up the Environment
- Setting up SQL Server
- Setting the Database Connect String
- Database Commit Modes
- Setting up the Synergy OpenNET Server
- Setting up the FileService Server
- Configuring the Replicator Environment
- Running Multiple Instances
- Changing Field Data Types
- Excluding Fields From Replication
- Excluding Keys from Replication
- Building the Sample Environment
- Running the Sample Programs
- On Windows
- On UNIX or Linux
- On OpenVMS
- FileService