MySQL Bugs: #42927: Wanted: list of statements that are unsafe for SBR

Bug #42927	Wanted: list of statements that are unsafe for SBR
Submitted:	17 Feb 2009 10:43	Modified:	22 Feb 2009 20:55
Reporter:	Sveta Smirnova	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S3 (Non-critical)
Version:	5.1, 6.0	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
There is no separate list of statements which fail with binlog format statement with message "Statement is not safe to log in statement format".

Although they are documented in different places in the user manual it is hard to find why one or other statement fails.

See bug #42851 for example.

How to repeat:
See description

Suggested fix:
Please make separate list of circumstances which can lead to warning/error "Statement is not safe to log in statement format"

Obviously intended for yours truly.

What you're actually asking for is a list of statements that are unsafe for SBR and thus cause the warning "Statement is not safe to log in statement format" if you try to replicate them using SBR in 5.1/6.0. I've updated the Synopsis to reflect this. Such a list already exists in "Comparison of Statement-Based and Row-Based Replication" (http://dev.mysql.com/doc/refman/5.1/en/replication-sbr-rbr.html), under "Disadvantages of Statement-Based Replication".

I don't see any reason to duplicate this list elsewhere (making info redundant makes it more difficult to keep all copies of that info in sync), but I've made some changes to make this more obvious:

* Grouped these statement together within a single heading "Statements which are unsafe for SBR" - it's now the first item under "Disadvantages of Statement-Based Replication".

* Added a note about the warning in the log following the list

* Added index terms to make it easier to find in the Index and in online searches.