[
https://issues.apache.org/jira/browse/LOG4J2-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16690156#comment-16690156
]
ASF subversion and git services commented on LOG4J2-2509:
---------------------------------------------------------
Commit ee517cbb4f1f031ea77b4f444c8828441e8d4a6b in logging-log4j2's branch
refs/heads/master from [~garydgregory]
[ https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;h=ee517cb ]
[LOG4J2-2509] Allow a JDBC Appender to truncate strings to match a
table's metadata column length limit. Not documenting truncateStrings
for now since it might make sense to always have it on.
> 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 Gregory
> Assignee: Gary Gregory
> Priority: Major
> Fix For: 3.0.0, 2.11.2
>
>
> 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
(v7.6.3#76005)
