10-09-2010
This is from the documentation of 5.0 (and I believe it's valid for 5.1 as well):
Quote:
23.5.9: Do triggers work with replication? Triggers and replication in MySQL 5.0 work in the same way as in most other database systems: Actions carried out through triggers on a master are not replicated to a slave server. Instead, triggers that exist on tables that reside on a MySQL master server need to be created on the corresponding tables on any MySQL slave servers so that the triggers activate on the slaves as well as the master.
For more information, see
Section 16.4.1.25, “Replication and Triggers”.
Replication and triggers should work as expected, I'm not sure if updating the same rows via statement and triggers on the same table (and at the same time) works though ...
8 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Our NIS master server went down. We have since fixed it and brought it back up. However all of are machines still point to the slave server when looking at it with ypwhich. My question is how do i point the servers back to the master.
Frank (2 Replies)
Discussion started by: frankkahle
2 Replies
2. SCO
hello , i setup a lan network , but i don't know how configure master and slave in the lan network please help me:confused: (2 Replies)
Discussion started by: hossein
2 Replies
3. AIX
Hello Everybody,
I have a question regarding SLAVE NIS SERVER in aix.
We are using NIS master of Sun Solaris 9.0 which is on different subnet i.e. 10.197.93.0. And Our slave server is having AIX 5.3 installed which is on 10.207.13.0 subnet.
I have a query regarding its name and ip address... (0 Replies)
Discussion started by: jit15975
0 Replies
4. Shell Programming and Scripting
i have a table
records
------------
id | user | time | event
91 admin | 12:00 | hi
92 admin | 11:00 | hi
93 admin | 12:00 | bye
94 admin | 13:00 | bye
95 root | 12:00 | hi
96 root | 12:30 | hi
97 root | 12:56 | hi
how could i only select and display only the user and event from... (6 Replies)
Discussion started by: kpddong
6 Replies
5. Programming
I am writing a process that has a master thread and a set of slave threads. Master thread is supposed to get jobs dynamically and assign to slave thread which is free. Master also get results back from slaves once a job is done. The number of slaves should be adjustable dynamically based on job... (1 Reply)
Discussion started by: tamil.pamaran
1 Replies
6. UNIX Desktop Questions & Answers
I have an application desigend in PHP and MySQl running on apache web server that I is running on a Amazon EC2 server Centos. I want to implement the master-master and master slave replication and high availability disaster recovery on this application database.
For this I have created two... (0 Replies)
Discussion started by: Palak Sharma
0 Replies
7. Programming
Hi,
How to wait the slave to be finished first then execute the master?
Can someone give me the specific function? Or the detailed example.
Thanks~ (1 Reply)
Discussion started by: wanliushao
1 Replies
8. IP Networking
Hey everyone. I'm creating a DNS master/slave server set up.
I have the configurations all done I believe, the master has the required zone file, and the named.conf file has the allow transfer and allow query stuff set. The slave has it's own configs set.
My question is that when initially... (1 Reply)
Discussion started by: Lost in Cyberia
1 Replies
LEARN ABOUT X11R4
deb-triggers
deb-triggers(5) dpkg suite deb-triggers(5)
NAME
deb-triggers - package triggers
SYNOPSIS
triggers
DESCRIPTION
A package declares its relationship to some trigger(s) by including a triggers file in its control archive (i.e. DEBIAN/triggers during
package creation).
This file contains directives, one per line. Leading and trailing whitespace and everything after the first # on any line will be trimmed,
and empty lines will be ignored.
The trigger control directives currently supported are:
interest trigger-name
interest-await trigger-name
interest-noawait trigger-name
Specifies that the package is interested in the named trigger. All triggers in which a package is interested must be listed using
this directive in the triggers control file. The "noawait" variant does not put the triggering packages in triggers-awaited state.
This should be used when the functionality provided by the trigger is not crucial.
activate trigger-name
activate-await trigger-name
activate-noawait trigger-name
Arranges that changes to this package's state will activate the specified trigger. The trigger will be activated at the start of the
following operations: unpack, configure, remove (including for the benefit of a conflicting package), purge and deconfigure. The
"noawait" variant does not put the triggering packages in triggers-awaited state. This should be used when the functionality
provided by the trigger is not crucial.
If this package disappears during the unpacking of another package the trigger will be activated when the disappearance is noted
towards the end of the unpack. Trigger processing, and transition from triggers-awaited to installed, does not cause activations.
In the case of unpack, triggers mentioned in both the old and new versions of the package will be activated.
Unknown directives are an error which will prevent installation of the package.
The "-noawait" variants should always be favored when possible since triggering packages are not put in triggers-awaited state and can thus
be immediately configured without requiring the processing of the trigger. If the triggering packages are dependencies of other upgraded
packages, it will avoid an early trigger processing run and make it possible to run the trigger only once as one of the last steps of the
upgrade.
The "-noawait" variants are supported since dpkg 1.16.1, and will lead to errors if used with an older dpkg.
The "-await" alias variants are supported since dpkg 1.17.21, and will lead to errors if used with an older dpkg.
SEE ALSO
dpkg-trigger(1), dpkg(1), /usr/share/doc/dpkg-dev/triggers.txt.gz.
1.19.0.5 2018-04-16 deb-triggers(5)