ports/98578: DBD-mysql 3.0004 bug causes warnings
Andrew McNaughton
andrew at scoop.co.nz
Tue Jun 6 05:55:02 UTC 2006
>Number: 98578
>Category: ports
>Synopsis: DBD-mysql 3.0004 bug causes warnings
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: freebsd-ports-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: change-request
>Submitter-Id: current-users
>Arrival-Date: Tue Jun 06 05:40:25 GMT 2006
>Closed-Date:
>Last-Modified:
>Originator: Andrew McNaughton
>Release: FreeBSD 5.4-RELEASE-p5 i386
>Organization:
Scoop Media (NZ) Ltd
>Environment:
System: FreeBSD io.scoop.co.nz 5.4-RELEASE-p5 FreeBSD 5.4-RELEASE-p5 #4: Fri Jul 22 04:55:48 NZST 2005 root at io.scoop.co.nz:/usr/obj/usr/src/sys/io i386
>Description:
using DBD-mysql version 3.0004, ordinary creation and destruction of Class::DBI objects causes warnings to be generated on standard out, reportedly due to a bug in DBD-mysql.
In my circumstances, this means close to a gigabyte per day of warnings piling up in Apache error logs, so I've had to back off to DBD-mysql 3.0003.
I'm not clear on what the implications will be for users of DBD-Mysql outside of Class::DBI.
Reportedly the problem has been fixed in the development version of DBD-mysql (3.0004_1 fixes it)
>From my notes, I think this is the URL for the discussion thread I found on this problem, but right now it says it's "Down for maintenance":
http://comments.gmane.org/gmane.comp.lang.perl.modules.class-dbi/6030
>How-To-Repeat:
Pretty much any use of Class::DBI with DBD-mysql-3.0004
>Fix:
Either back off to DBD-mysql version 3.0003, or use fixes from the development version of the module.
>Release-Note:
>Audit-Trail:
>Unformatted:
More information about the freebsd-ports-bugs
mailing list