D]
Sent: Tuesday, May 11, 2004 8:16 AM
To: Log4J Users List
Subject: RE: Logging to Database: max column size
At 02:49 PM 5/11/2004, James Stauffer wrote:
>Thanks. That should solve that stack trace size problem. I assume
>then even though the comment in the code says varchar(256) I could
At 02:49 PM 5/11/2004, James Stauffer wrote:
Thanks. That should solve that stack trace size problem. I assume then
even though the comment in the code says varchar(256) I could increase that
up to varchar(4000) if I desire.
Sure, you can increase the size of the field when you create the table
I handle that? I actually wouldn't
care if the value was truncated at some reasonable limit.
James Stauffer
-Original Message-
From: Ceki Gülcü [mailto:[EMAIL PROTECTED]
Sent: Tuesday, May 11, 2004 2:51 AM
To: Log4J Users List
Subject: RE: Logging to Database: max column size
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 datab
: 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 datab
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
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
