Sven Sandberg 94946c6807 BUG#49222: Mark RAND() as unsafe ... Problem: When RAND() is binlogged in statement mode, the seed is binlogged too, so the replication slave generates the same sequence of random numbers. This makes replication work in many cases, but not in all cases: the order of rows is not guaranteed for, e.g., UPDATE or INSERT...SELECT statements, so the row data will be different if master and slave retrieve the rows in different orders. Fix: Mark RAND() as unsafe. It will generate a warning if binlog_format=STATEMENT and switch to row-logging if binlog_format=ROW.		2010-01-13 10:00:03 +01:00
..
r	BUG#49222: Mark RAND() as unsafe	2010-01-13 10:00:03 +01:00
std_data	Bug#47323 : mysqlbinlog --verbose displays bad output when events contain subset of columns	2009-10-09 16:54:48 +08:00
t	BUG#49222: Mark RAND() as unsafe	2010-01-13 10:00:03 +01:00
combinations	WL#4350 Options in my.cnf style config file should not start with --	2008-09-05 15:31:09 +02:00