There is an example in examples/ directory. Adding a new conversion
character is indeed a natural continuation of your current approach
which I must say is ill advised.
Escaping quotes is one issue that PreparedStatements solve trivially.
PreparedStatements are a mandatory part of the JDBC spec while Batch
statements are optional. MySQL does support PreparedStatements.
Log4j components have to be absolutely reliable. There are many cool
features that we do not implement because they cannot be implemented
reliably. JDBCAppender must adhere to the same guidelines.
At 11:47 06.06.2002 -0700, Kevin Steppe wrote:
>After digging into the throwable info in a JDBCAppender a littler here is
>my current idea:
>
>Use an extension to the PatternLayout, which can convert the throwable
>into a single string (with colons, or \n, or whatever in between). This
>new conversion character code then be placed in the normal sql such as:
>insert into log (message, trace) values ('%m', '%throw')
>
>I remeber reading that custom conversions are fairly easy. Anyone have a
>pointer for me?
>
>Kevin
--
Ceki
SUICIDE BOMBING - A CRIME AGAINST HUMANITY
Sign the petition: http://www.petitiononline.com/1234567b
I am signatory number 22106. What is your number?
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
