You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by James Stauffer <js...@spscommerce.com> on 2004/05/18 17:07:16 UTC
DBAppender logging_event.level_string
For DBAppender the column logging_event.level_string is defined as
varchar(254). As I understand it the possible values are: DEBUG, INFO,
WARN, ERROR, and FATAL, so it seems that varchar(5) would big enough. If
someone wanted to define a CRITICAL level then making it varchar(10) would
give plenty of room. Why is it so big?
James Stauffer
Re: DBAppender logging_event.level_string
Posted by Ceki Gülcü <ce...@qos.ch>.
Hi James,
The field is 254 long in order to support custom Level types. The support
is not there yet but it will be added eventually.
At 05:07 PM 5/18/2004, you wrote:
>For DBAppender the column logging_event.level_string is defined as
>varchar(254). As I understand it the possible values are: DEBUG, INFO,
>WARN, ERROR, and FATAL, so it seems that varchar(5) would big enough. If
>someone wanted to define a CRITICAL level then making it varchar(10) would
>give plenty of room. Why is it so big?
>
>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: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org