View Revisions: Issue #5476
| Summary | 0005476: Ability to disable sync triggers when sync on incoming is enabled | ||
|---|---|---|---|
| Revision | 2022-09-28 16:19 by elong | ||
| Description | Provide a way to disable the sync triggers even when sync on incoming is enabled. When sync on incoming is enabled for a trigger, the text of the trigger uses a condition of 1=1 so the trigger will always fire. Each database platform has a session variable that can be set to 1 to disable the triggers. When sync on incoming is disabled, the text of the trigger tests that the session variable is null. Update the trigger text to test that the session variable is not 2 when sync on incoming is disabled. That way, the trigger will fire when the session variable is null (local change) or 1 (loading data sync), but not if the user sets it to 2. Initial implementation for Oracle, SQL Server, MySQL, and PostgreSQL. |
||
| Revision | 2022-09-28 16:17 by elong | ||
| Description | Provide a way to disable the sync triggers even when sync on incoming is enabled. When sync on incoming is enabled for a trigger, the text of the trigger uses a condition of 1=1 so the trigger will always fire. Each database platform has a session variable that can be set to 1 to disable the triggers. When sync on incoming is disabled, the text of the trigger tests that the session variable is null. Update the trigger text to test that the session variable is not 2 when sync on incoming is disabled. That way, the trigger will fire when the session variable is null (local change) or 1 (loading data sync), but not if the user sets it to 2. | ||