Bug #81171 Improve documentation related to sql_mode NO_AUTO_CREATE_USER

• Submitted: 21 Apr 2016 14:15
• Modified: 29 Oct 2017 23:35
• Reporter: Simon Mudd (OCA)
• Status: Closed
• Category: MySQL Server: Documentation
• Severity: S3 (Non-critical)
• Version: 5.7
• OS: Any
• CPU Architecture: Any
• Tags: no_auto_create_user, SQL_MODE

[21 Apr 2016 14:15] Simon Mudd

Description:
I notice in: http://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sqlmode_no_auto_create_user a reference:

" NO_AUTO_CREATE_USER will be removed in a future MySQL release, at which point its effect will be enabled at all times (GRANT will not create accounts)."

One of the reasons for not enabling this setting was that it was not replication safe.
In MySQL 5.7 that changed and the syntax of DROP USER, CREATE USER were modified and ALTER USER added in a way that were replication safe.

That is there is now
DROP USER IF EXISTS ...
CREATE USER IF NOT EXISTS ...
ALTER USER IF EXISTS ...

How to repeat:
See above.

Suggested fix:
It may be worth making some reference to the fact that this "new syntax" allows people even in a replication environment to safely use these commands without fear that they may break replication on a slave which for some reason may be configured with different grants to the grants on the master.

So please add this extra context, and add a link to the commands for reference.

[22 Apr 2016 6:51] MySQL Verification Team

Hello Simon,

Thank you for the report and feedback!

Thanks,
Umesh

[29 Oct 2017 23:35] Paul DuBois

Posted by developer:
 
https://dev.mysql.com/doc/refman/5.7/en/sql-mode.html#sqlmode_no_auto_create_user updated.