Hi Francesco,
Could you explaine the problem. I don't see your problem.
Now this feature run (see and test whith TestISXXXXXXEnable.sql)
Hi,
I try to explain more clearly the problem.
The bug was a bug in all function isXXXXXXEnable in version . As you can see, for instance in function isFatalEnabled
FUNCTION isFatalEnabled ( pCTX IN LOG_CTX ) RETURN boolean is begin return islevelEnabled(pCTX, getLevelInText('FATAL')); end;
there is a call to getLevelInText whereas the correct call is getTextInLevel.
The call used inside the plog version 312 does not work and give a conversion error from text to integer. The fix to this bug is to replace the getLevelInText calls inside isXXXXEnabled the with getTextInLevel calls.
I olso get a lot confused when I search for this error since the name of the two function getLevelInText and getTextInLevel are similar and the oracle error was a bit cryptic.
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Log4plsql-all-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/log4plsql-all-info log4plsq : http://log4plsql.sourceforge.net
