Thank you for explanations!

Re ALWAYS triggers, I have an AFTER trigger on some tables that writes an
audit-trail record to a change_log table. That only happens in the "Main"
database. But if a data modification happens in the "Child" database, which
is also a Source/Master DB, then the Main DB doesn't want to fire that
audit-trail trigger (upon bucardo replication) unless I make the audit-trail
trigger an ALWAYS trigger.

Am I doing it wrong? 

-----Original Message-----
From: Greg Sabino Mullane [mailto:[email protected]] 
Sent: Friday, August 01, 2014 10:21 PM
To: Jonathan Brinkman
Cc: [email protected]
Subject: Re: [Bucardo-general] bucardo 5 install guide - swap syncs


Setting a trigger to ALWAYS should almost never be needed. Certainly not in
the normal course of Bucardo usage.

--
Greg Sabino Mullane [email protected]
End Point Corporation
PGP Key: 0x14964AC8

_______________________________________________
Bucardo-general mailing list
[email protected]
https://mail.endcrypt.com/mailman/listinfo/bucardo-general

Reply via email to