Bug #21553 RFE: CREATE TRIGGER ... SELECT ON ...

Submitted: 9 Aug 2006 20:52 Modified: 29 Jul 2008 16:57
Reporter: Kevin Benton (Candidate Quality Contributor) Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Server: Stored Routines Severity:S4 (Feature request)
Version:5.0.24 OS:Any
Assigned to: CPU Architecture:Any

[9 Aug 2006 20:52] Kevin Benton 
Description:
Please add new functionality - CREATE TRIGGER ... SELECT ON ...  This will allow us to log when users are looking at sensitive data...

How to repeat:
See Description

Suggested fix:
See Description
[28 Aug 2006 11:43] Valeriy Kravchuk 
Thank you for a feature request. Sorry, but this is against SQL standard, so I am not sure it will be ever implemented. One day you'll be able to use view + stored function in view definition to do things like that...
[29 Jul 2008 16:57] Kevin Benton 
Please consider suggesting to DBA training team that the workaround for this is to use stored procedures to grant access to data in tables where a trigger on select is needed.  Seems I remember reading and article recently that Oracle, DB2, PgSQL, DB2 and MS-SQL all allow trigger on select.  I just think it's strange that MySQL has chosen to reject it (and apparently based on other comments, so has the standard).
[20 Nov 2015 7:30] Daniël van Eeden 
A newer RFE for the same issue:
https://bugs.mysql.com/bug.php?id=72395

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.