when you create MYSQL replication mater that has the newer version than slave this will create compatibility issue, due some changes in the binary logs and SQL base, your workaround may solve the issue for now, but you will encounter many issues in the future

SQL incompatibilities: You cannot replicate from a newer master to an older slave using statement-based replication if the statements to be replicated use SQL features available on the master but not on the slave.

Use of row-based replication: Row-based replication was implemented in MySQL 5.1.5, so you cannot replicate using row-based replication from any MySQL 5.5 or later master to a slave older than MySQL 5.1.5.

references : http://dev.mysql.com/doc/refman/5.5/en/replication-compatibility.html

Should master and slave have same mysql version?

suggested solutions:

1. upgrade Master version to the same version as slave. best solution

2. skip slave error slave-skip-errors= (not the best solution I will leave it to the last option)

when you create MYSQL replication mater that has the newer version than slave this will create compatibility issue, due some changes in the binary logs and SQL base, your workaround may solve the issue for now, but you will encounter many issues in the future

SQL incompatibilities: You cannot replicate from a newer master to an older slave using statement-based replication if the statements to be replicated use SQL features available on the master but not on the slave.

Use of row-based replication: Row-based replication was implemented in MySQL 5.1.5, so you cannot replicate using row-based replication from any MySQL 5.5 or later master to a slave older than MySQL 5.1.5.

references : http://dev.mysql.com/doc/refman/5.5/en/replication-compatibility.html

Should master and slave have same mysql version?

suggested solutions:

1. upgrade Master version to the same version as slave. best solution

2. skip slave error slave-skip-errors= (not the best solution I will leave it to the last option)

when you create MYSQL replication mater that has the newer version than slave this will create compatibility issue, due some changes in the binary logs and SQL base, your workaround may solve the issue for now, but you will encounter many issues in the future

SQL incompatibilities: You cannot replicate from a newer master to an older slave using statement-based replication if the statements to be replicated use SQL features available on the master but not on the slave.

Use of row-based replication: Row-based replication was implemented in MySQL 5.1.5, so you cannot replicate using row-based replication from any MySQL 5.5 or later master to a slave older than MySQL 5.1.5.

references : http://dev.mysql.com/doc/refman/5.5/en/replication-compatibility.html

Should master and slave have same mysql version?

when you create MYSQL replication mater that has the newer version than slave this will create compatibility issue, due some changes in the binary logs and SQL base, your workaround may solve the issue for now, but you will encounter many issues in the future

SQL incompatibilities: You cannot replicate from a newer master to an older slave using statement-based replication if the statements to be replicated use SQL features available on the master but not on the slave.

Use of row-based replication: Row-based replication was implemented in MySQL 5.1.5, so you cannot replicate using row-based replication from any MySQL 5.5 or later master to a slave older than MySQL 5.1.5.

references : http://dev.mysql.com/doc/refman/5.5/en/replication-compatibility.html

Should master and slave have same mysql version?

suggested solutions:

1. upgrade Master version to the same version as slave. best solution

2. skip slave error slave-skip-errors= (not the best solution I will leave it to the last option)