Bug #19783 | triggers are triggered on just single node in clustered table | ||
---|---|---|---|
Submitted: | 12 May 2006 19:27 | Modified: | 12 May 2006 21:31 |
Reporter: | johnny slakva | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Cluster: Cluster (NDB) storage engine | Severity: | S4 (Feature request) |
Version: | mysql-5.0 | OS: | Linux (RHEL3) |
Assigned to: | CPU Architecture: | Any | |
Tags: | 5.0.21 |
[12 May 2006 19:27]
johnny slakva
[12 May 2006 21:31]
Hartmut Holzgraefe
This is expected behavior, triggers act on the SQL level and the SQL part of the query is executed in the mysqld server the client issuing the query is connected to. Only the actual data is replicated to all connected mysqld api nodes but not the query changing the data. This could possibly be solved by a NDBAPI application using the clusters internal notification event mechanism. I'm keeping this bug report as a feature request as it might make sense to implement this on the SQL level at a later stage, too, but don't expect this to be implemented anytime soon ...