Could you show the exact code that produces the problem?

With the following test I can't replicate the issue:

#!/usr/bin/perl -l
use DBIx::Log4perl qw(:masks);

$DBIx::Log4perl::LogMask = DBIX_L4P_LOG_OUTPUT | DBIX_L4P_LOG_INPUT;

print $DBIx::Log4perl::LogMask;
[download]

(prints '3', as expected)

I used:

use DBIx::Log4perl qw(:masks);

$DBIx::Log4perl::LogMask = DBIX_L4P_LOG_OUTPUT | DBIX_L4P_LOG_INPUT;

Log::Log4perl->init("myconfig.cfg");

$dbh = DBIx::Log4perl->connect($DSN, "user", "pass");
[download]

Config-file:

log4perl.logger = FATAL, LOGFILE

log4perl.appender.LOGFILE=Log::Log4perl::Appender::File
log4perl.appender.LOGFILE.filename=logs/FATAL.TXT
log4perl.appender.LOGFILE.mode=append
log4perl.appender.LOGFILE.Threshold = ERROR

log4perl.appender.LOGFILE.layout=PatternLayout
log4perl.appender.LOGFILE.layout.ConversionPattern=[%r] %F %L %c - %m%
+n

log4perl.logger.DBIx.Log4perl=DEBUG, A1
log4perl.appender.A1=Log::Log4perl::Appender::File
log4perl.appender.A1.filename=logs/OK.txt
log4perl.appender.A1.mode=append
log4perl.appender.A1.layout=Log::Log4perl::Layout::SimpleLayout
[download]

From a quick look at the code, I would say try replacing line 277 in DBIx/Log4perl/st.pm

    $sth->_dbix_l4p_perl(2,              # line 277
        sub {Data::Dumper->Dump(
            [$res],
            ["fetchrow_hashref($h->{dbh_no}.$sth->{private_DBIx_st_no}
+)"])})
        if ($h->{logmask} & DBIX_L4P_LOG_OUTPUT);
[download]

with

    $sth->_dbix_l4p_debug($h, 2,         # line 277
        ...
[download]

AFAICT, there is no method _dbix_l4p_perl in any of the related packages (while there are similarly named ones like ..._debug, ..._info, etc.).  No guarantees, though (untested).

...and of course it worked:-) Thanks a lot!
Should I file a bug report to the author about this?

That was a bug in DBIx::Log4perl and is fixed in 0.22 which I've just uploaded. I didn't see your thread even though I am a perl monk because your subject did not grab me and I don't have time to read every one - perhaps there is a lesson to be learnt there. The fix correctly identified elsewhere in this thread is trivial and a little embarrassing although I have to admit to not using the OUTPUT logging in my own projects.

The subject did start out as something else - I wanted to learn how to use constants:) But I can see that v0.22 works "from scratch" after installing it on a new machine.