The fact that you write to a DB will always make the process slower (than writting to a file) per se. Now many elements should be considered (DB has huge memory, multi process, IO's in C/C++ versus pure Java) to confirm this but I can afford a small performance impact to gain system wide improved reporting, facility, ... ! ! !
What I found funny is that nobody mentionned the work of the jdbc-appender http://www.dankomannhaupt.de/projects/ Their tables looks more appropriate for Java than the simple tables of Log4plsql. I think I will inspire myself from the code of Heri and adapt the work of the log4plsql to have NDC in the table too ! \T, -- Any fool can write code that a computer can understand. Good programmers write code that humans can understand. Martin Fowler T. : +32 (0)2 742 05 94 M. : +32 (0)497 44 68 12 @ : [EMAIL PROTECTED] Do you skype too ... ? ----- Original Message ---- From: Bender Heri <[EMAIL PROTECTED]> To: Log4J Users List <log4j-user@logging.apache.org> Sent: Wednesday, March 8, 2006 2:54:57 PM Subject: RE: Using the same tables for log4j with JDBC appender and Log4PLSQL I have not noticed a performance impact, since we log only WARN, ERROR, and FATAL into DB. And this occurs not that often. Heri > -----Original Message----- > From: Rakesh Patel [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 08, 2006 2:50 PM > To: Log4J Users List > Subject: Re: Using the same tables for log4j with JDBC appender and > Log4PLSQL > > > Thank you, what about performance? > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
