Bug #11055 information_schema: routines.sql_data_access has wrong value

Submitted: 2 Jun 2005 23:43 Modified: 23 Jun 2005 21:54
Reporter: Peter Gulutzan Email Updates:
Status: Closed Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.0.7-beta-debug OS:Linux (SUSE 9.2)
Assigned to: Sergei Glukhov CPU Architecture:Any

[2 Jun 2005 23:43] Peter Gulutzan
Description:
In information_schema.routines, the possible values of the sql_data_access column are:
'NO SQL', 'CONTAINS SQL', 'READS SQL DATA', 'MODIFIES SQL DATA'.
But the value I see is: ''.

How to repeat:
mysql> create procedure pix () modifies sql data set @a = 5;
Query OK, 0 rows affected (0.01 sec)

mysql> select sql_data_access from information_schema.routines where specific_name='pix';
+-----------------+
| sql_data_access |
+-----------------+
|                 |
+-----------------+
1 row in set (0.03 sec)
[2 Jun 2005 23:49] Jorge del Conde
I was able to reproduce this using 5.0.7 from bk:

mysql> create procedure pix () modifies sql data set @a = 5;
Query OK, 0 rows affected, 2 warnings (0.02 sec)

mysql> select sql_data_access from information_schema.routines where
    -> specific_name='pix';
+-----------------+
| sql_data_access |
+-----------------+
|                 |
+-----------------+
1 row in set (0.00 sec)
[7 Jun 2005 8:50] Bugs System
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/internals/25677
[16 Jun 2005 7:13] Sergei Glukhov
Fixed in 5.0.8
[16 Jun 2005 15:09] Bugs System
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/internals/26064
[23 Jun 2005 21:54] Mike Hillyer
Documented in 5.0.8 changelog.

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.040 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.