Bug #48510 Flag for allow/disallow set password without SUPER priv and documentation update

Submitted:	3 Nov 2009 17:10	Modified:	8 Jan 2011 0:20
Reporter:	Roger David Nay	Email Updates:
Status:	Closed	Impact on me:	None
Category:	MySQL Server: Documentation	Severity:	S2 (Serious)
Version:	5.0+	OS:	Any
Assigned to:	Jon Stephens	CPU Architecture:	Any

Description:
Customers have 5.0 to 5.1 replication. The different behaviour for set password between versions using read_only GLOBAL variable can cause a problem here.

See related bug http://bugs.mysql.com/bug.php?id=27440

There is no mention of the 5.0 which allows a user to change their password in the 5.0 documentation. There is also no mention of this in the 5.1 documentation either.

How to repeat:
See http://bugs.mysql.com/bug.php?id=27440

Suggested fix:
Either a change to 5.0/5.1 to allow/disallow this with a variable.

A documentation change explaining that 5.0 has the exception of allowing the update in the 5.0 AND 5.1 documentation.

Thank you for the feature request.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

Re-opening. Seems I misinterpreted some things.

Thank you for your bug report. This issue has been addressed in the documentation. The updated documentation will appear on our website shortly, and will be included in the next release of the relevant products.

Commit which fixes this properly is here:

http://lists.mysql.com/commits/128209

Page generated in 0.057 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.