Skip Menu |

This queue is for tickets about the DBD-mysql CPAN distribution.

Report information
The Basics
Id: 68146
Status: rejected
Priority: 0/
Queue: DBD-mysql

Owner: Nobody in particular
Requestors: jaded_phoenix_62 [...]

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: (no value)

Subject: Addition of profiling code to DBD::mysql
Date: Thu, 12 May 2011 15:07:42 +0100
To: <bug-dbd-mysql [...]>
From: Michael Ramnarine <jaded_phoenix_62 [...]>
Download (untitled) / with headers
text/plain 541b
Hi, I am interested in adding automatic profiling to DBD::mysql. This, when active, would enable profiling on the server and output queries where certain criteria are met, such as length of execution time. This could be implemented in a way that would be configurable using callback semantics. A full implementation may be dependant on multiple statement handles handling multiple results sets simultaneously. This issue is described in ticket 68119 . Any thoughts or feedback would be appreciated. Thanks in advance, Mike
Download (untitled) / with headers
text/plain 681b
Hi Mike, I think mysql has pretty decent support for profiling already in the database, using 'SET profiling=1;' and 'SHOW PROFILE;': Also, on a different level, DBI itself comes with a nice profiler: I'm not so sure DBD::mysql should have additional profiling code. Of course, you could be right: feel free to hack on DBD::mysql, to show some code, show us how it could work! I'm not **against** adding stuff in DBD::mysql. Just be aware that there are already tools available, both at the database level and on the perl DBI level. -- Michiel

This service is sponsored and maintained by Best Practical Solutions and runs on infrastructure.

Please report any issues with to