Bug #12866 No accessible transaction id within triggers
| Submitted: | 30 Aug 2005 3:11 | Modified: | 14 Oct 2009 9:09 |
|---|---|---|---|
| Reporter: | Frank McGeough | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: General | Severity: | S4 (Feature request) |
| Version: | 5.0.11 | OS: | Windows (Windows 2003 server) |
| Assigned to: | CPU Architecture: | Any |
[30 Aug 2005 3:11]
Frank McGeough
[3 Sep 2005 0:09]
RW Shore
I need this as well.
[2 Feb 2009 10:19]
Jaka JanÄar
+1, if it means anything.
[14 Oct 2009 9:09]
Valeriy Kravchuk
Thank you for the feature request.
[1 Mar 2010 22:50]
Patrick Hammer
The same here. Feature absolutely requested. Overall, if one wants to support Oracle and MySQL. The complete system is based on Oracle and we would like to have a full support of MySQL. However, without this feature, the MySQL support for our applications is a no-go.
[13 Mar 2012 20:24]
Michael Mior
Should this not be doable using the XID used in XA support? (i.e. something from the return value of thd_get_xid()) The base64-encoded value of data could work, although this could be 100+ chars long.
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.