Replication bug again

Hi all,

I was of the opinion that the foreign_key_checks problem that came
during the mysql replication during importing the DB on master server
will be solved in the 4.0.13 release but it is still not working and I
am getting failed replication with error No. 150 on the slave when there
is an import going on the Master server.

Sohail




--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: Replication bug again

On Thu, 2003-05-22 at 10:48, Sohail Hasan wrote:
> Hi all,
>
> I was of the opinion that the foreign_key_checks problem that came
> during the mysql replication during importing the DB on master server
> will be solved in the 4.0.13 release but it is still not working and I
> am getting failed replication with error No. 150 on the slave when there
> is an import going on the Master server.

Dear Hasan,

Unfortunately this is not the bug which is to be fixed in 4.0.x release.
It is documented in replication deficiencies section and will be fixed
in MySQL 5.0

Currently we do not have logging of SET commands at all and it requires
plenty of changes to do it properly.



--
Are you MySQL certified?, http://www.mysql.com/certification/
__ ___ ___ ____ __
/ |/ /_ __/ __/ __ \/ / Peter Zaitsev
/ /|_/ / // /\ \/ /_/ / /__ MySQL AB, Full-Time Developer
/_/ /_/\_, /___/\___\_\___/ Moscow, Russia
<___/ www.mysql.com


--
MySQL Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org