on 2010 Oct 07 2:38 PM
When a stored procedure runs a DROP CONNECTION against the connection currently in use by an event, the following message appears in the console log:
User "DBA" dropped event connection 1000001154 ("victim-event-name")
In some (most) environments, that may be important, but in others (mine) these messages are just annoying... the DROPs are frequently and automatically executed under the covers as part of business-as-usual.
Suggestion: allow these messages to be suppressed on a case-by-case basis; e.g., add a clause to the CREATE EVENT statement, or a clause to the event's EXCEPTION block, or something coded at the victim-event level to say "don't fret if my connection is dropped".
Request clarification before answering.
This issue sounds related to your other recent posting related to events - Do not display “Statement interrupted by user” event exceptions when database is shutting down - and perhaps the solution to that issue can also resolve this request as well?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
46 | |
6 | |
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.