On Mon, Jul 30, 2007 at 06:19:09PM -0400, Perrin Harkins wrote:
> On 7/30/07, Matt S Trout <[EMAIL PROTECTED]> wrote:
> > I used to consider it a neat hack. After some time with the internals,
> > some fun explicitly disabling it within DBIC since it sometimes broke our
> > reconnect code, and even then discovering I could often solve client
> > mod_perl
> > problems by removing the line that loaded it from httpd.conf, I reclassified
> > it was 'awful'.
>
> Your implication is that Apache::DBI doesn't work, as opposed to
> simply clashing with some of the DBIC code that tries to manage the
> same connections. It works just fine. It's widely-used and does what
> it was intended to without known bugs.
Except in the DBIx::Class, Class::DBI and plain DBI apps I've brought back
to production quality stability by removing it.
There's no "implication" - sometimes it doesn't work. Mostly it does. Producing
a repeatable test case has proven pretty much impossible due to the hackiness
of the implementation. Since I usually -can- modify the calling code I
just switch it over to using a DBIC storage object to manage the $dbh and
move on.
--
Matt S Trout Need help with your Catalyst or DBIx::Class project?
Technical Director Want a managed development or deployment platform?
Shadowcat Systems Ltd. Contact mst (at) shadowcatsystems.co.uk for a quote
http://chainsawblues.vox.com/ http://www.shadowcat.co.uk/
_______________________________________________
List: Catalyst@lists.rawmode.org
Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst
Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/
Dev site: http://dev.catalyst.perl.org/
