MySQL Bugs: #65097: Replication using SBL

Bug #65097	Replication using SBL
Submitted:	25 Apr 2012 7:10	Modified:	25 Apr 2012 7:28
Reporter:	Mannoj S	Email Updates:
Status:	Not a Bug	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	5.1.61	OS:	Linux
Assigned to:		CPU Architecture:	Any
Tags:	SBL

Description:
Hi Team MySQL, 

Are non-deterministic values/functions like uuid(), sysdate() are handled in Statement Based Logging to have the same fields as generated from master log to the binlog? If so which version onwards is suitable for master/slave replication that are robust in data accuracy for SBL? I didn't find much docs on which version onwards this has been corrected. 

I care about data consistency and accuracy. But I'm pretyy much comfortable with SBL or do you say to get rid of this should I have to live with RBL/Mixed? 

Regards,
Mannoj

How to repeat:
It repeats only when uuid() and sysdate() are used by my developers. 

Suggested fix:
I do see now() is updating correctly for logs from master to bin logs under SBL.
I can see the value has been parsed as a variable in binlog>sql. 

from binlog > sql
insert into test values (now())
/*!*/;
# at 541
#120418 16:28:56 server id 1  end_log_pos 623   Query   thread_id=472   exec_time=0     error_code=0

Please correct if my understanding is wrong. When I use the above bin log files and create a clone or update a physical dr I works fine . This kinda parsing variable can be efficient fix for other non-deterministic variables. Whats your thot?

We're sorry, but the bug system is not the appropriate forum for asking help on using MySQL products. Your problem is not the result of a bug. You can find answers to your questions at http://dev.mysql.com/doc/refman/5.5/en/replication-sbr-rbr.html.

Support on using our products is available both free in our forums at http://forums.mysql.com/ and for a reasonable fee direct from our skilled support engineers at http://www.mysql.com/support/

Thank you for your interest in MySQL.