----- Original Message ----- > > However, this does not seem to replicate to the slave, and no error > > shows > > Have you compared the slave's relay logs and master's binary logs? Does > this query present in both logs?
The hint was what I needed, Gleb. Spasibo. It turns out that the administrator doing this is using an elderly version of SQLyog to run his scripts, and either by accident or design, SQLyog doesn't make entries in the master bin-log - so no replication is ever going to happen. The query (actually a set of queries) don't appear in logs on either server. This GUI has been in use for over a year, but we only switched on the replication system a couple of weeks ago, and this is the first 'occasional' update - that was frequently used on the old master-only system without problems. Thanks again for the hint! Terry >See: > http://dev.mysql.com/doc/mysql/en/slave-logs.html > http://dev.mysql.com/doc/mysql/en/Binary_log.html > http://dev.mysql.com/doc/mysql/en/mysqlbinlog.html > > > > Terry Riley <[EMAIL PROTECTED]> wrote: > > We are running 4.1.13 standard on Linux as a master, and 4.1.14 on > > NT4 as a slave. > > > > Replication seems to work extremely well, except in the following > > circumstance. > > > > On the master server, running a query similar to: > > > > insert into zmast.leagueinfo > > (countieslist, defaultleaguecode, leaguename .......) > > select > > countieslist, 'DDLS2005', leaguename ...... > > from zmast.leagueinfo > > where defaultleaguecode='ddls2004'. > > > > using the same table as source and target, with the only changes > > being the defaultleaguecode and the autoincrement ID field, without > > any problem. > > > > However, this does not seem to replicate to the slave, and no error > > shows until later when an attempt is made to insert a record into a > > table where a relationship to this record is required ('Cannot update > > child record'-type message). > > > > The manual that I have does specify that "currently you cannot insert > > into a table and select from the same table in a subquery." Clearly > > this is not actually the case, but for some reason, it will not > > replicate. > > > > Anyone else had/got this problem? > > > > Is there a sensible solution - the only one I can come up with is > > changing the intitial 'insert ... select' into a 'create table temp > > select from...'/'insert ... select from temp'/ 'drop table temp' set. > > > > This insert ... select stuff is not done on a regular basis, and then > > only by an administrator. > > > > Ideas welcome........ > > > > Cheers > > Terry -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
