file: $CPAN/authors/id/T/TI/TIMB/DBI-1.56_91.tar.gz
size: 489501 bytes
md5: 0a690df4e157ce8de4862bc019d3c9f6
=head2 Changes in DBI 1.57 (svn rev 9639), 13th June 2007
Fixed XS versions of select*_*() methods to call execute()
fetch() etc., with inner handle instead of outer.
Fixed execute_for_fetch() to not cache errstr values
thanks to Bart Degryse.
Fixed unused var compiler warning thanks to JDHEDDEN.
Fixed t/86gofer_fail tests to be less likely to fail falsely.
Corrected timeout example in docs thanks to Egmont Koblinger.
Changed t/01basic.t to warn instead of failing when it detects
a problem with Math::BigInt (some recent versions have been buggy).
Added extra trace info to connect_cached thanks to Walery Studennikov.
Added non-random (deterministic) mode to DBI_GOFER_RANDOM mechanism.
Added DBIXS_REVISION macro that drivers can use.
DBI::Profile changes:
Added support for !Time and !Time~N (N-sec granular) in Path.
Don't profile DESTROY during global destruction.
Added as_node_path_list() and as_text() methods and tests.
DBI::ProfileDumper changes:
Don't write file if there's no profile data.
Uses full natural precision when saving data (was using %.6f)
Optimized flush_to_disk().
Locks the data file while writing.
Enabled filename to be a code ref for dynamic names.
DBI::ProfileDumper::Apache changes:
Added Quiet=>1 to avoid write to STDERR in flush_to_disk().
Added Dir=>... to specify a writable destination directory.
Enabled DBI_PROFILE_APACHE_LOG_DIR for mod_perl 1 as well as 2.
Added parent pid to default data file name.
DBI::ProfileData changes:
Added DeleteFiles option to delete files once read.
Locks the data files while reading.
Added ability to sort by Path elements.
dbiprof changes:
Added --dumpnodes and --delete options.
Added/updated docs for both DBI::ProfileDumper && ::Apache.
=cut
You can see the primary focus of my recent developments for Shopzilla
have been around profiling. Specifically using the DBI's profiling
mechanisms to implement lightweight always-on application-level profiling.
I've a new module, called DashProfiler, that I expect to release this
week that provides a simple/flexible/efficient way to add performance
tracking to an application, especially web applications. (It happens to
use DBI handles internally to store profile data but is unrelated to databases.)
As usual, I'd appreciate any and all testing you can do.
Thanks!
Tim.
p.s. Uploaded to CPAN at 13 Jun 2007 16:45:35 GMT.
May take a few hours or more to reach whatever mirror you use.
