Bug #68111 No documentation about Grantor field in tables_priv
Submitted: 17 Jan 2013 20:08 Modified: 29 Jan 2013 17:27
Reporter: Sveta Smirnova Email Updates:
Status: Closed Impact on me:
Category:MySQL Server: Documentation Severity:S3 (Non-critical)
Version:5.5.31, 5.7.1 OS:Any
Assigned to: Paul DuBois CPU Architecture:Any

[17 Jan 2013 20:08] Sveta Smirnova
At http://dev.mysql.com/doc/refman/5.5/en/grant-table-structure.html our user manual claims: "The Timestamp and Grantor columns currently are unused and are discussed no further here. "

However, working on bug #68074 I found it is filled most likely by value, returned by function USER().

This means we should have clarify this value in the manual.

How to repeat:
See description
[29 Jan 2013 14:50] Paul DuBois
"This means we should have clarify this value in the manual."

For what purpose? Just because the value is set to something doesn't necessarily mean that the value is ever used for anything later.

If you know otherwise, please indicate how it's used so the manual can be updated properly.
[29 Jan 2013 16:42] Sveta Smirnova
Please see description of bug #68074

Use found that content of his tables on master and slave is different. Only difference is GRANTOR column. We have following problems here:

1. CHECKSUM TABLE and other tools will report master and slave are inconsistent.
2. User doesn't know if s/he can ignore this inconsistency.
3. Bug verifier can not define if this is replication bug or not.

If content of GRANTOR column is documented, all these issues can be solved.
[29 Jan 2013 17:27] Paul DuBois
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.

The Timestamp and Grantor columns are set to the current timestamp
and the CURRENT_USER value, respectively. However, they are unused
and are discussed no further here.