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

[Ceki Gulcu (JIRA)]

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

Ceki Gulcu commented on LBCLASSIC-169:
--------------------------------------

There is no need to have this assigned to you. Just do it. See also http://articles.qos.ch/contributing.html

You are probably more interested in fixing LBCLASSIC-188. If you intend to override the way  table names and columns are resolved, I strongly suggest adding a DBNameResolver as explained in LBCLASSIC-188.

> 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