logging-log4j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matt Sicker (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (LOG4J2-734) Add JDBC batch update support when supported
Date Wed, 23 Jul 2014 16:03:41 GMT

    [ https://issues.apache.org/jira/browse/LOG4J2-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071890#comment-14071890

Matt Sicker commented on LOG4J2-734:

I agree in regards to semantic versions at least. I could back out the change so we can add
it to 2.1. That way I can also add some additional configuration for it (such as being able
to disable it completely).

> Add JDBC batch update support when supported
> --------------------------------------------
>                 Key: LOG4J2-734
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-734
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 2.0
>            Reporter: Matt Sicker
>            Assignee: Matt Sicker
> This would be especially useful for the flush() method in the database manager class.
The way the code is currently structured, this looks like it would work out rather well, too.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org

View raw message