On Mon, Jan 13, 2003 at 09:41:12AM +1000, Jason Brooke wrote:
> No, I've been ignored on this problem for 18 months now, for some reason.
> Quite peculiar.
> 

The limitations of replicate-do-db are documented in:

http://www.mysql.com/doc/en/Replication_Options.html

I found out about this limitation the hard way, just like you seem to
have done. Since we don't control the scripts that use the database,
we couldn't use replicate-do-db. It just takes too much time to fix the
problems when someone forgets about this limitation.


Regards,

Fred.


> ----- Original Message -----
> From: "Ross Davis - DataAnywhere.net" <[EMAIL PROTECTED]>
> To: "'Jason Brooke'" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Sent: Monday, January 13, 2003 9:16 AM
> Subject: RE: Replication bug?
> 
> 
> > Did you ever get any confirmation that it will be added to the official
> > bug list?
> >
> > -----Original Message-----
> > From: Jason Brooke [mailto:[EMAIL PROTECTED]]
> > Sent: Sunday, January 12, 2003 3:14 AM
> > To: Ross Davis - DataAnywhere.net
> > Cc: [EMAIL PROTECTED]
> > Subject: Re: Replication bug?
> >
> >
> > Yes this is the same issue I've reported previously. Unless literally
> > 'select' the database, the query is never written to the binary log.
> >
> >
> > ----- Original Message -----
> > From: "Ross Davis - DataAnywhere.net" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Sunday, January 12, 2003 12:38 PM
> > Subject: Replication bug?
> >
> >
> > > I think I have found a replication bug.  We are using Mysql-Max
> > > 3.23.53 in a master and multiple slave situation.  That is working
> > > fine.  We are using InnoDB
> > >
> > > We have found a workaround to the problem but I thought you should
> > > know about it.
> > >
> > > We have 2 databases on the system call them dba and dbb.
> > >
> > > If I have a connection to dba and and then run the following query the
> >
> > > update happens on the master but not on the slaves!!!
> > >
> > > replace into dbb.tablename set field='somevalue' ...
> > >
> > > The key to the problem is not the replace into, but the fact that we
> > > are connected to one database and working on another.
> 
> 
> 
> 
> ---------------------------------------------------------------------
> Before posting, please check:
>    http://www.mysql.com/manual.php   (the manual)
>    http://lists.mysql.com/           (the list archive)
> 
> To request this thread, e-mail <[EMAIL PROTECTED]>
> To unsubscribe, e-mail <[EMAIL PROTECTED]>
> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
> 

-- 
Fred van Engen                              XB Networks B.V.
email: [EMAIL PROTECTED]                Televisieweg 2
tel: +31 36 5462400                         1322 AC  Almere
fax: +31 36 5462424                         The Netherlands

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)

To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

Reply via email to