[jira] [Commented] (LOG4J2-2509) Allow a JDBC Appender to truncate strings to match a table's metadata column length limit

["Volkan Yazici (Jira)" <ji...@apache.org>]

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

Volkan Yazici commented on LOG4J2-2509:
---------------------------------------

[~ggregory], shall we move this ticket from a _bug_ to _improvement_? The use case makes total sense to me. What is the state of the change set? Is there anything else that needs to be implemented?

> Allow a JDBC Appender to truncate strings to match a table's metadata column length limit
> -----------------------------------------------------------------------------------------
>
>                 Key: LOG4J2-2509
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-2509
>             Project: Log4j 2
>          Issue Type: Bug
>          Components: Appenders
>            Reporter: Gary D. Gregory
>            Assignee: Gary D. Gregory
>            Priority: Major
>             Fix For: 3.0.0, 2.15.0
>
>
> Allow a JDBC Appender to truncate strings to match a table's metadata column length limit.
> Some databases like MySQL can be configured to cause SQL INSERT statements to fail when data for a column exceeds the length of a column definition.
> In the case of MySQL 8, this is the default configuration, and asking a DB admin to change this to accommodate an application is not reasonable.
> This feature would add a new attribute on the {{JdbcAppender}} called {{truncateStrings}} which would do so. This would be set to true by default for a smooth initial impression.
>  



--
This message was sent by Atlassian Jira
(v8.3.4#803005)