Bug #17244 GRANT gives strange error message when used in a stored function

Description:
When using a GRANT inside a stored procedure, a strange error message is printed. If row-based replication is enabled, the changes to the mysql.user table is logged to the binary log.

How to repeat:
CREATE FUNCTION foo(x INT)
    RETURNS INT
BEGIN
    GRANT SELECT ON t1 TO mysqltest@localhost;
    RETURN x;
END

mysql> SELECT foo(3);
ERROR 1100 (HY000): Table 'user' was not locked with LOCK TABLES

It is not a stored procedure, as I wrote, it is a stored function. The example is still correct.

Hartmut, why didn't you verify it using the earliest version possible?

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

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

A patch for this bug has been committed. After review, it may
be pushed to the relevant source trees for release in the next
version. You can access the patch from:

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

Fixed by the patch for Bug#21975 Grant and revoke statements are non-transactional

Pushed into 5.1.23-beta

Noted in 5.1.23 changelog.

Incompatible change: GRANT and REVOKE statements now cause an
implicit commit, and thus are prohibited within stored functions and
triggers.