Help - Search - Members - Calendar
Full Version: Sqlyog With Replication Environment
Webyog Forums > SQLyog > Using SQLyog
alan.cooper
We are using SQLYog with 3-server circular replication environment.

We are intermittently seeing problems with the replication breaking and we think this is to do with the syntax SQLYog uses.

e.g. The manual states (http://dev.mysql.com/doc/refman/5.0/en/replication-rules.html) that creates should be in the form:

use 'dbname';
create table 'tablename (blah)';

But SQLYog creates the syntax as

use 'dbname';
create table 'dbname.tablename(blah)';

It seems to be explicitely specifiying the tabel name that's causing replication issues.

IS there any way to ammend the syntax (without manually going through the generated SQL?)


Many thanks for your help
peterlaursen
Is that link correct? I do not think I find such rule/advice on that page (except for the user comment at the bottom).
Could you elaborate?


Actually we have a replication setup between this server (webyog.com - Master) and a server at our office in Bangalore (Slave).
I frequently do manipulations on Master with SQLyog as well as a PHP script (an internal maintenance routine we have developed for ourselves). That never broke replication as far as I know! Most of those are inserts/updates but also create's have occurred.


Do you think it is a problem due to the circular replication pattern, or is it 'create table' statement and other specific statements only where this is a problem?

What does 'break replication' mean? Does replication gets completely disabled or is it this particular statement only that fails to replicate?

I will not exclude anything! But it would be a problem with thousands of 'standard applications' too, if this is correct!




... and there is no way to configure this. This is all compiled into the program.
peterlaursen
additional comments/questions:


1) It would be easy to verify this by executing "create table `database`.`table` ... ;" from command line. Did you?

2) One thing that is known to break circular replication is that if you have auto_increment columns you must use the 'auto_increment_increment' construction to avoid PK collisions.

3) Please tell server versions and more details about this setup. Any particular 'recipe' or 'guidelines' that were followed?
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.
Invision Power Board © 2001-2008 Invision Power Services, Inc.