You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@logging.apache.org by "Ralph Goers (Jira)" <ji...@apache.org> on 2021/12/11 16:38:00 UTC
[jira] [Updated] (LOG4J2-2509) Allow a JDBC Appender to truncate strings to match a table's metadata column length limit
[ https://issues.apache.org/jira/browse/LOG4J2-2509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ralph Goers updated LOG4J2-2509:
--------------------------------
Fix Version/s: 2.16.0
(was: 2.15.0)
> 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.16.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.20.1#820001)