> Stored functions execute with the same NOW() value as the calling statement. However, this is not true of stored procedures.
That's from the "disadvantages of statement-based replication" section, not the row-based replication section. So to recap, the disadvantages you've quoted from the manual are specific to statement-based replication, which is deprecated.
> Don't forget about the pitfalls of replicating CREATE USER and ALTER USER in MySQL
As mentioned in that Percona blog post, all you need to do is add IF EXISTS / IF NOT EXISTS to your SQL and it solves the problem. Or in MariaDB, you also have the option of CREATE OR REPLACE syntax.
Sure, it's a minor footgun for newbies, but not exactly a horrendous problem.
Statement-based replication is deprecated: https://dev.mysql.com/doc/refman/8.0/en/replication-options-...
> Stored functions execute with the same NOW() value as the calling statement. However, this is not true of stored procedures.
That's from the "disadvantages of statement-based replication" section, not the row-based replication section. So to recap, the disadvantages you've quoted from the manual are specific to statement-based replication, which is deprecated.
> Don't forget about the pitfalls of replicating CREATE USER and ALTER USER in MySQL
As mentioned in that Percona blog post, all you need to do is add IF EXISTS / IF NOT EXISTS to your SQL and it solves the problem. Or in MariaDB, you also have the option of CREATE OR REPLACE syntax.
Sure, it's a minor footgun for newbies, but not exactly a horrendous problem.