FW: Replication bug

How-To-Repeat:

-----Original Message-----
From: bugs@lists.mysql.com [mailto:bugs@lists.mysql.com]
Sent: Tuesday, January 14, 2003 2:39 PM
To: Ross Davis - DataAnywhere.net
Subject: Re: Replication bug


Your message cannot be posted to bugs@lists.mysql.com because it did not
follow the format expected by our spam/off-topic filter. To this list we
accept only repeatable bugs reports, meaning that you can describe a set
of steps we can follow to repeat the bug on our systems.

If you are having problems with MySQL but are unable to provide the
required description, and have not purchased a support contract from
MySQL AB, you should send your message to mysql@lists.mysql.com and
possibly one of our knowledgable users or developers will help you.
However, we do not guarantee that every message on mysql@lists.mysql.com
will be answered. We can afford to provide free code, but unfortunately,
we cannot afford to provide guaranteed free support on top of that. We
do, nevertheless, fix our bugs regardless of who reports them and whose
systems they affect, and will investigate your problem if you can prove
to us with a test case that the error is in our code and not yours.

If you have purchased a support contract from MySQL AB, you should
follow the standard support request procedure to report this problem.
Support contracts are available at https://order.mysql.com/.

If you are able to describe how we can repeat the problem, include the
string "How-To-Repeat:" in the body of your message, followed by the
detailed description of what we need to do to make it happen, and our
filter will accept your message. If you use mysqlbug script, which comes
with the MySQL distribution, to post the message, it will be
automatically accepted.

You have written the following:

---start of your message----
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.

I posted this message to the newsgroup and there were other comments
around the same type of problems but nothing from a Mysql person so I
thought I should send it in.




---end of your message-------

MySQL Development Team


------------------------------------------------------------ ---------
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 bugs-thread13481@lists.mysql.com
To unsubscribe, e-mail

Re: statement not replicated in 3.23.53 if the db is not selected

Dear Sir,

First of all, as our lists management agent said,

> Your message cannot be posted to bugs@lists.mysql.com because it did not
> follow the format expected by our spam/off-topic filter. To this list we
> accept only repeatable bugs reports, meaning that you can describe a set
> of steps we can follow to repeat the bug on our systems.

Please be kind to us and follow this advice next time.

Now about your problem, I'd like to have more info from you :

1) Could you send
the my.ini and output of SHOW VARIABLES
for your master and your slave.
Also the output of SHOW MASTER STATUS
on your master
and SHOW SLAVE STATUS on your slave ?
On which OS are your master/slave running ?

2) And explain which of the options below you use on
your slave, and the value of these :
replicate-do-table
replicate-ignore-table
replicate-wild-do-table
replicate-wild-ignore-table
replicate-ignore-db
replicate-do-db
replicate-rewrite-db

3) And explain which of the options below you use on
your master, and the value of these :
binlog-do-db
binlog-ignore-db

4) And send a testcase : something like
CREATE TABLE ...
USE ...
REPLACE INTO ...
which is not replicated.

Thanks.
You can reply to me and CC:bugs@lists.mysql.com.

--
For technical support contracts, visit https://order.mysql.com/?ref=mgbi
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Mr. Guilhem Bichot
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Software Developer
/_/ /_/\_, /___/\___\_\___/ Bordeaux, France
<___/ www.mysql.com +33 5 56 88 34 39
--

On Tuesday 14 January 2003 23:44, Ross Davis - DataAnywhere.net wrote:
> 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 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 bugs-thread13485@lists.mysql.com
To unsubscribe, e-mail