[logback-dev] [JIRA] Commented: (LBCLASSIC-169) DBAppender redesign [was originally: Customizing table names used by DbAppender]

[Tomasz Nurkiewicz (JIRA)]

    [ http://jira.qos.ch/browse/LBCLASSIC-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=11608#action_11608 ] 

Tomasz Nurkiewicz commented on LBCLASSIC-169:
---------------------------------------------

My idea was to have multiple DbAppenders, each writing to a completely separate set of logging tables, dedicated to each appender. The tables would have different names and each DbAppender would choose the target tables via logback.xml configuration file. Now table names are hard-coded, so even when creating multiple DbAppenders, they all use the same logging tables. Please assign me to LBCLASSIC-188, I can implement this feature.

> DBAppender redesign [was originally: Customizing table names used by DbAppender]
> --------------------------------------------------------------------------------
>
>                 Key: LBCLASSIC-169
>                 URL: http://jira.qos.ch/browse/LBCLASSIC-169
>             Project: logback-classic
>          Issue Type: Improvement
>          Components: appender
>    Affects Versions: 0.9.18
>            Reporter: Tomasz Nurkiewicz
>            Assignee: Ceki Gulcu
>            Priority: Minor
>
> ch.qos.logback.classic.db.DBAppender uses hard-coded table names for logging events: logging_event, logging_event_property and logging_event_exception. Allowing to change these default names has two benefits:
> * There are systems where database table names must follow some naming conventions (prefixes, using underscores vs. camel case)
> * One could create several Db appenders, each operating on different set of tables (for performance reasons or more fine grained logging and filtering)
> Each table name would be configured using a property in logback.xml. Default values for table names would be the same as present ones to maintain backward compatibility. If you are interested in this feature let me know, I can implement it and provide a patch.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.qos.ch/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira