post-push fixes for BUG#39934: updating test cases

mysql-test/r/partition_innodb_stmt.result:
  Error message changed.
mysql-test/r/sp_trans.result:
  Error message changed.
mysql-test/suite/binlog/r/binlog_stm_unsafe_warning.result:
  Error message changed.
mysql-test/suite/binlog/t/binlog_unsafe.test:
  Test now uses udf's, so needs to source include/have_udf.inc
mysql-test/suite/parts/r/rpl_partition.result:
  updated result file
mysql-test/suite/parts/t/rpl_partition.test:
  We no longer allow a slave that has binlog_format=statement
  to execute row events. Hence we force the slave to have
  binlog_format=row.
mysql-test/suite/rpl_ndb/t/rpl_ndb_binlog_format_errors.test:
  The test uses the example plugin, hence it must
  source include/have_example_plugin.inc.

1 files changed, 2 insertions, 2 deletions

diff --git a/mysql-test/suite/binlog/r/binlog_stm_unsafe_warning.result b/mysql-test/suite/binlog/r/binlog_stm_unsafe_warning.result
index 439bff0cfe1..f6c8d6421bc 100644
--- a/mysql-test/suite/binlog/r/binlog_stm_unsafe_warning.result
+++ b/mysql-test/suite/binlog/r/binlog_stm_unsafe_warning.result
@@ -4,10 +4,10 @@ CREATE TABLE t1 (a int, b int, primary key (a));
 INSERT INTO t1 VALUES (1,2), (2,3);
 UPDATE t1 SET b='4' WHERE a=1 LIMIT 1;
 Warnings:
-Note	1592	Statement may not be safe to log in statement format.
+Note	1592	Unsafe statement binlogged in statement format since BINLOG_FORMAT = STATEMENT. Statement: UPDATE t1 SET b='4' WHERE a=1 LIMIT 1
 UPDATE t1 SET b='5' WHERE a=2 ORDER BY a LIMIT 1;
 Warnings:
-Note	1592	Statement may not be safe to log in statement format.
+Note	1592	Unsafe statement binlogged in statement format since BINLOG_FORMAT = STATEMENT. Statement: UPDATE t1 SET b='5' WHERE a=2 ORDER BY a LIMIT 1
 DROP TABLE t1;
 ### NOT filtered database => assertion: binlog disabled and warnings ARE NOT shown
 SET SQL_LOG_BIN= 0;