Bug #20200 View docs are inconsistent about SQL SECURITY clause

• Submitted: 1 Jun 2006 13:12
• Modified: 1 Jun 2006 19:14
• Reporter: Baron Schwartz (Basic Quality Contributor)
• Status: Not a Bug
• Category: MySQL Server: Documentation
• Severity: S3 (Non-critical)
• Version: 5.0 and 5.1
• OS: Any (all)
• Assigned to: Paul DuBois
• CPU Architecture: Any

[1 Jun 2006 13:12] Baron Schwartz

Description:
The documentation for 5.0 and 5.1 don't agree on when the DEFINER and SQL SECURITY clauses were added.

From http://dev.mysql.com/doc/refman/5.0/en/create-view.html:

The DEFINER and SQL SECURITY  clauses specify the security context to be used when checking access privileges at view invocation time. They were addded in MySQL 5.0.13, but have no effect until MySQL 5.0.16.

From http://dev.mysql.com/doc/refman/5.1/en/create-view.html:

The DEFINER and SQL SECURITY  clauses specify the security context to be used when checking access privileges at view invocation time. They were addded in MySQL 5.1.2.

How to repeat:
This is not a behavior bug.

[1 Jun 2006 13:16] Baron Schwartz

There are also several other places on these documents where the version numbers are mentioned, such as:  "As of MySQL 5.0.16 (when the DEFINER and SQL SECURITY clauses were implemented)"

[1 Jun 2006 13:26] MySQL Verification Team

Thank you for the bug report.

[1 Jun 2006 13:39] Paul DuBois

In the 5.0 manual, the version number indicates
when the change was made to MySQL 5.0.

In the 5.1 manual, the version number indicates
when the change was made to MySQL 5.1.