Thanks. I updated and see the change. It appears you write each line to a distinct record so that you can support very long stack traces. Is that correct?
-----Original Message----- From: Ceki Gülcü [mailto:[EMAIL PROTECTED] Sent: Monday, May 10, 2004 12:12 PM To: Log4J Users List Subject: Re: Logging to Database: max column size DBAppender which is not even checked in yet, logs exceptions to its own table worth each trace line having its own row. I am working on it right now. It should be available very soon. At 06:54 PM 5/10/2004, James Stauffer wrote: >Do any of the database appenders log a LogEvent even if one of the pieces of >data is too big to fit in that field? i.e. In Oracle a varchar2 can be up >to 4000 characters (without using a different way to write the data), but if >a insert a logging event with a message more than 4000 characters the insert >fails. From what I remember MS SQL just truncates the data (which would be >fine with me). I know that 4000 characters seems like a lot but our stack >trace messages can be very verbose (have all of the data from a document). >Is this issue handled by any database loggers? > >James Stauffer -- Ceki Gülcü For log4j documentation consider "The complete log4j manual" ISBN: 2970036908 http://www.qos.ch/shop/products/clm_t.jsp --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
