Bug #19794 | Stored Procedures: No way to "print" log messages to clients | ||
---|---|---|---|
Submitted: | 13 May 2006 12:48 | Modified: | 3 Oct 2008 9:09 |
Reporter: | Paul Medynski | Email Updates: | |
Status: | Verified | Impact on me: | |
Category: | MySQL Server: Stored Routines | Severity: | S4 (Feature request) |
Version: | 5.1.7-beta-log | OS: | Linux (Linux 2.4.27-2-386) |
Assigned to: | CPU Architecture: | Any |
[13 May 2006 12:48]
Paul Medynski
[15 May 2006 20:30]
Valeriy Kravchuk
Thank you for a feature request. For logging, why not just to INSERT you messages into (temporary, HEAP, MyISAM) a table, with timestamp and (for non-temporary table) session ID? Then your client application (or you, from another session) can just SELECT any part of that messages log (and delete messages, if not needed any more). Oracle's DBMS_OUTPUT package (used for SPs debugging) is working in that way. Yopu can create a nice SP called "print" for that, if you want.
[15 Jun 2006 23:00]
Bugs System
No feedback was provided for this bug for over a month, so it is being suspended automatically. If you are able to provide the information that was originally requested, please do so and change the status of the bug back to "Open".
[3 Oct 2008 9:10]
Valeriy Kravchuk
Bug #32747 was marked as a duplicate of this one.