[Dbix-class] ->deploy() trashes Log4perl configuration?

Jess Robinson castaway at desert-island.me.uk
Sun May 27 19:56:42 GMT 2007



On Thu, 24 May 2007, Jon Schutz wrote:

> On Thu, 2007-05-24 at 09:38 +0100, Jess Robinson wrote:
>> On Thu, 24 May 2007, Adrian Corston wrote:
>>
>>> Adrian Corston wrote:
>>>>
>>>>  The following example code shows that Log4perl's configuration is being
>>>>  trashed when calling ->deploy().  The failure behaviour is demonstrated by
>>>>  the lack of a "debug after" debug message.
>>>>
>>>
>>> mst says "if bits of SQLT fail please post patches to the DBIC list" so here
>>> is patch and a test.
>>>
>>
>> Thanks, but..
>>
>> I'm reluctant to apply a patch that "just removes the offending bit"
>> without explanations of what that does, and why removing it doesnt break
>> things.. Does that really solve your problem? I thought SQLT only loaded
>> the Parser/Producer currently being used, which shouldn't be Graph.
>>
>
> It's actually not a Parser/Producer that's in question here.
>
> SQL::Translator::Schema::Graph seems to be an internal representation of
> the schema.
>
> Adam's proposal of
>
>> use Log::Log4perl qw(:easy);
>> Log::Log4perl->easy_init($ERROR) unless Log::Log4perl->initialized;
>
> looks like a safe alternative.
>

Oh, it's a Schema thingy.. I wonder why.. ah well, yes, that does look 
saner, thanks.. I'll chuck it in there.

Jess




More information about the Dbix-class mailing list