Thanks Niall, let me know what you find. I'm only concerned because isn't it a significant performance hit for log4net to try and lookup the class name, method name, and all that? That's what I was trying to avoid.
Simon. -----Original message----- From: Niall Daley [EMAIL PROTECTED] Date: Thu, 08 Dec 2005 20:12:49 -0800 To: Log4NET User [email protected] Subject: [Spam] Re: onlyFixPartialEventData=true, but partial data still logged > Simon, > Setting onlyFixPartialEventData tells log4net to fix certain > elements of the data, not to ignore everything else. This means that > although you haven't fixed, for instance, the ClassName log4net will > attempt to identify it anyway. This probably isn't the desired behaviour, > I've raised a bug regarding this (see > http://issues.apache.org/jira/browse/LOG4NET-62) and I'll look in to it in > the next couple of days. > > Niall > > On Thu, 8 Dec 2005, Simon Wallis wrote: > > > Has anyone else experienced this, or know why this might be happening? > > > > Simon. > > > > -----Original message----- > > From: "Simon Wallis" [EMAIL PROTECTED] > > Date: Tue, 29 Nov 2005 17:40:13 -0800 > > To: [email protected] > > Subject: onlyFixPartialEventData=true, but partial data still logged > > > > > Hi, > > > > > > I'm setting onlyFixPartialEventData=true in my config file and am > > > using an ADONetAppender (log4net 1.2.8). In my appender config > > > settings I have parameters for ClassName, MethodName, FileName, and > > > LineNumber, but shouldn't these be NULL in the database since > > > onlyFixPartialEventData is equal to true? It seems these values are > > > getting logged when I don't want them to be (in production). > > > > > > Thanks, > > > Simon. > > > > -- > Niall Daley > Log4net Dev >
