Bug #18161 SHOW CREATE TRIGGER, SHOW TRIGGER STATUS

Submitted: 12 Mar 2006 1:31 Modified: 30 Sep 2008 14:49
Reporter: Markus Popp Email Updates:
Status: Won't fix Impact on me:
None 
Category:MySQL Server Severity:S4 (Feature request)
Version:5.1 OS:Any (all)
Assigned to: Marc ALFF CPU Architecture:Any
Tags: trigger

[12 Mar 2006 1:31] Markus Popp 
Description:
It would be intuitive to introduce 

SHOW CREATE TRIGGER
SHOW TRIGGER STATUS and
DROP TRIGGER IF EXISTS

commands the same way as with PROCEDURE and FUNCTION.

How to repeat:
Issue the mentioned commands.
[23 Mar 2006 17:10] Valeriy Kravchuk 
Thank you for a reasonable feature requests.
[28 Jun 2006 22:44] Marc Alff 
Posted a proposed patch today (2006-06-28) on the internal mailing list.

See http://lists.mysql.com/internals/33687

Marc Alff.
[12 Oct 2006 5:10] Marc ALFF 
Signed and sent the CLA (Contribution License Agreement),
covering this contribution.
[1 Nov 2006 9:44] Konstantin Osipov 
Setting back to in progress as I asked the implementor to supply a separate patch for DROP TRIGGER IF EXISTS. The rest of the code can not be pushed at this point and will have to be re-done later.

Thank you for your interest in MySQL!
[7 Nov 2006 0:29] Marc ALFF 
See the related Bug#23703 for DROP TRIGGER IF EXISTS
[4 Dec 2006 22:27] Marc ALFF 
DROP TRIGGER IF EXISTS has been fixed.
Changing the report to 'to be fixed later' for the remaining items.
[8 Feb 2007 19:01] Jonathan Haddad 
Is there any update on when this will be done?  Are there any workarounds in the meantime of generating valid SQL automatically?
[30 Sep 2008 14:49] Konstantin Osipov 
SHOW CREATE TRIGGER has been implemented.
SHOW TRIGGER STATUS is redundant, please use INFORMATION_SCHEMA.TRIGGERS instead.
[30 Sep 2008 14:50] Konstantin Osipov 
SHOW CREATE TRIGGER is present starting from 5.1:
http://dev.mysql.com/doc/refman/5.1/en/show-create-trigger.html

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

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