Bug #31623 | Lost ability to trace driver | ||
---|---|---|---|
Submitted: | 15 Oct 2007 22:46 | Modified: | 15 Oct 2007 23:02 |
Reporter: | Jared S (Silver Quality Contributor) | Email Updates: | |
Status: | Not a Bug | Impact on me: | |
Category: | Connector / ODBC | Severity: | S3 (Non-critical) |
Version: | 3.51.21 | OS: | Windows (Vista) |
Assigned to: | CPU Architecture: | Any | |
Tags: | debug, driver, trace |
[15 Oct 2007 22:46]
Jared S
[15 Oct 2007 22:47]
Jared S
DriverTracing
Attachment: TraceOption.jpg (image/pjpeg, text), 37.57 KiB.
[15 Oct 2007 23:02]
Kent Boortz
Sorry for us being unclear, the trace functionality in question is the "manager trace" that saves in a log the manager calls to the driver. The driver trace functionality in the driver itself was removed a few releases back, as the manager trace be used to create a similar log file.
[15 Oct 2007 23:18]
MySQL Verification Team
Please see: http://dev.mysql.com/doc/refman/5.0/en/myodbc-configuration-trace.html Thanks in advance.