Mailing-List: contact log4j-dev-help@logging.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Log4J Developers List" <log4j-dev@logging.apache.org>
Date: Tue, 18 Oct 2016 15:26:58 +0000 (UTC)
From: "Badreddine BENAIDJA (JIRA)" <jira@apache.org>
To: log4j-dev@logging.apache.org
Message-ID: <JIRA.12673659.1381742343000.17369.1476804418440@Atlassian.JIRA>
In-Reply-To: <JIRA.12673659.1381742343000@Atlassian.JIRA>
References: <JIRA.12673659.1381742343000@Atlassian.JIRA> <JIRA.12673659.1381742343830@arcas>
Subject: [jira] [Commented] (LOG4J2-424) JDBCAppender: Add support for data
 types other then String
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 18 Oct 2016 15:27:00 -0000


    [ https://issues.apache.org/jira/browse/LOG4J2-424?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1558=
5747#comment-15585747 ]=20

Badreddine BENAIDJA commented on LOG4J2-424:
--------------------------------------------

[~mikael.staldal@home.se] you mean Thread Context ?

> JDBCAppender: Add support for data types other then String
> ----------------------------------------------------------
>
>                 Key: LOG4J2-424
>                 URL: https://issues.apache.org/jira/browse/LOG4J2-424
>             Project: Log4j 2
>          Issue Type: Improvement
>          Components: Appenders
>    Affects Versions: 2.0-beta9
>         Environment: All
>            Reporter: Tihomir Me=C5=A1=C4=8Di=C4=87
>            Assignee: Nick Williams
>
> I am using the JDBCAppender to log to a Postgresql database. I have a tab=
le (log_entries) that's used for logging purposes.=20
> One of the attributes is of type INTEGER. The attribute is something spec=
ific for our application and we are using ThreadContext (MDC) to set the va=
lue of the parameter.
> Currently, log4j provides no support for integer type attributes in the C=
olumn element of the JDBC appender configuration (the only types supported =
are string (default), timestamp - isEventTimestamp flag and Clob - isClob f=
lag).
> When using the default settings in the Column element of the JDBC appende=
r, log4j will create a prepared statement and try to set the value using th=
e Statement.setString() method. Of course, the JDBC driver throws an except=
ion:
> Caused by: org.postgresql.util.PSQLException: ERROR: column "mn_type_d" i=
s of type integer but expression is of type character varying
>   Hint: You will need to rewrite or cast the expression.
> My appender configuration:
>     <JDBC name=3D"jdbcAppender" tableName=3D"log_entries">
>       <DriverManager url=3D"jdbc:postgresql://10.28.10.32:5432/xxx" usern=
ame=3D"xxx" password=3D"xxx" />
>       <Column name=3D"log_entries_id" literal=3D"nextval('hibernate_seque=
nce')" />
>     =20
>       .....
>       <Column name=3D"message" isUnicode=3D"false" pattern=3D"%message" /=
>
>       <Column name=3D"mn_type_d" isUnicode=3D"false" pattern=3D"%X{mn_typ=
e_d}" /> <-- this is of type integer in the DB but LOG4J tries to insert it=
 as a String  -->
>     </JDBC>


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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