MySQL Bugs: #20930: Mixed binlogging mode does not work with stored functions, triggers, views

Bug #20930	Mixed binlogging mode does not work with stored functions, triggers, views
Submitted:	9 Jul 2006 14:27	Modified:	18 Aug 2006 16:56
Reporter:	Guilhem Bichot	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Replication	Severity:	S3 (Non-critical)
Version:	5.1-bk	OS:	Linux (linux)
Assigned to:	Guilhem Bichot	CPU Architecture:	Any

Description:
As documented in our manual, the mixed mode does not apply to stored functions (inside stored functions, we don't switch to row-based binary logging even if it would be needed).
Now I am removing this limitation. This is needed as we decided to fix
BUG#19630 "stored function inserting into two auto_increment
 breaks statement-based binlog" by saying that in mixed mode, these functions will use row-based binlogging.

How to repeat:
create a stored function using UUID() in its body, call it, see that UUID() was not replicated well on slave

Bug also existed if trigger or view had UUID() in their body

Pushed into replication team tree, will be in 5.1.12
"Mixed binlogging mode does not work with stored
  functions, triggers, views", which was a documented limitation (in mixed
  mode, we didn't detect that a stored function's execution needed row-based
  binlogging (due to some UUID() call for example); same for
  triggers, same for views (a view created from a SELECT UUID(), and doing
  INSERT INTO sometable SELECT theview; would not replicate row-based).
Now it works.
This:
http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html
must be fixed.
ChangeSet
  guilhem@gbichot3.local|ChangeSet|20060709150047|19215    2006/07/09 17:00:47+02:00 guilhem@gbichot3.local +15 -0
  * Mixed replication mode * :
... (note that the changeset comment has a typo as it talks about 20630, it's
really 20930.

Noted in 5.1.12 changelog.

Added a note to the "Replication Features and Problems" section
noting the limitation and that it has been lifted in 5.1.12.