| Bug #24286 | Triggers should be able to callback | ||
|---|---|---|---|
| Submitted: | 14 Nov 2006 6:59 | Modified: | 26 Dec 2006 11:39 |
| Reporter: | Morgan Tocker | Email Updates: | |
| Status: | Verified | Impact on me: | |
| Category: | MySQL Server: Stored Routines | Severity: | S4 (Feature request) |
| Version: | 5.2+ | OS: | |
| Assigned to: | CPU Architecture: | Any | |
[26 Dec 2006 11:39]
Valeriy Kravchuk
Thank you for a reasonable feature request.
Description: If you run in an extremely high READ environment, the write cost of the trigger is minimal. Having it be able to send a message (either via CLI, java method) to an application will mean that it can update/destroy cache for example. (Think of how often a category definitions tables would change). How to repeat: * Create a trigger. * Try and make it talk to your application Suggested fix: This can currently be emulated by writing a UDF that can talk back to your application via SQL functions. i.e. SELECT send_message('SQL_STRING_HERE'); What I am asking is that this become standardised as part of the core functionality.