on 2017 May 15 10:54 AM
I have a pair of synchronized databases using mobilink using shadow tables on cons. side. As long as I know all the changes caused by triggers will not be transfered between databases (are written as comments in transaction log files). For some reason I have all the new entries inserted through trigger this time in both directions replicated. Is this an option?
Request clarification before answering.
Dbmlsync will only send trigger actions to the consolidated if the SendTriggers externded options is set to ON. The deafult is off. If dbmlsync is sending trigger actions, check the value of this externded option.
When MobiLink determines the rows to download to the remote database, it is likely just executing a SELECT statement on a table, so it doesn't matter at that point whether the value is in the table as a result of a trigger or not.
Reg
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'll bet you actually remember how that works without looking it up every single time, right? ( unlike me 🙂
Hi Reg, Yes, on the consolidated side we are using shadow table containing primary key of the table + last_modified, which means that on the cons. even the through trigger coming changes will be included in synchronisation and will be sent to remote.
About the synchronisation from remote side, I am not yet sure, I will test it and write again.
Sarkis
He means Reg.
User | Count |
---|---|
87 | |
10 | |
9 | |
9 | |
7 | |
6 | |
6 | |
5 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.