I'm also interested in this code, thanks
Fr�d�ric ----- Original Message ----- From: <[EMAIL PROTECTED]> To: "Log4J Users List" <[EMAIL PROTECTED]> Sent: Thursday, June 20, 2002 3:07 PM Subject: RE: Log4j JDBCAppender > > I'd like a copy as well. [EMAIL PROTECTED] > Thanks, > Steve > > > > > |---------+----------------------------> > | | "Tumpach, Andrew | > | | J" | > | | <[EMAIL PROTECTED]| > | | om> | > | | | > | | 06/20/2002 08:56 | > | | AM | > | | Please respond to| > | | "Log4J Users | > | | List" | > | | | > |---------+----------------------------> > >--------------------------------------------------------------------------- -----------------------------------| > | | > | To: "Log4J Users List" <[EMAIL PROTECTED]> | > | cc: | > | Subject: RE: Log4j JDBCAppender | > >--------------------------------------------------------------------------- -----------------------------------| > > > > > Kevin, > > I've received permission to donate code outside the company. :) Please let > me know where to send source. Ceki, if you'd like to have a look, perhaps > some of it will be helpful towards the new JdbcAppender? Anyone else? > > Andrew > > -----Original Message----- > From: Tumpach, Andrew J > Sent: Tuesday, June 18, 2002 12:51 PM > To: Log4J Users List > Subject: RE: Log4j JDBCAppender > > > Kevin, > > I'd personally be glad to share the code. Unfortunately, since it's > company property, I have to get permission from the powers that be before I > can release source code outside the company. Hopefully it won't take to > long for my request to wend it's way through the bureaucracy. :( > > I haven't seen problems yet with setObject, but I'm assuming it will take > feedback from users of a variety of databases and drivers in order to know > if this will work across the board. > > Re. the stored procs, I don't know - I'm guessing it's partly due to > perceptions about increasing workload for our DBAs, or possibly lack of > support in previous versions. > > Andrew > > -----Original Message----- > From: Kevin Steppe [mailto:[EMAIL PROTECTED]] > Sent: Monday, June 17, 2002 4:59 PM > To: Log4J Users List > Subject: RE: Log4j JDBCAppender > > > Andrew, > If you're willing, I'd love to see the code. I like > your idea of the comma-separated keys and would like > to see how you've implemented it. > If setObject will work for all types then that will > be the way to go. For my own enlightenment, why would > a company prevent developers from using a stored proc. > for repeatedly executed sql? > > Kevin > > --- "Tumpach, Andrew J" <[EMAIL PROTECTED]> wrote: > > I've extended the JDBCAppender to do > > PreparedStatement work. Here's a synopsis: pass in > > a Hashtable as the message, with multiple database > > columns' values in it. A new property in the log4j > > property file contains comma-separated keys (in the > > order used in the SQL statement) used to pull values > > out of the Hashtable. Re #1 below, > > PreparedStatement.setObject() works just fine so > > far. Re #2, escaping is not an issue with Prep. > > Stmts. Re #5, some shops don't let developers do > > stored procs. My main problem right now is Ceki's > > declaration of the uncertain future of JDBCAppender. > > :) > > > > Andrew > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED] > > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED] > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED] > > > For additional commands, e-mail: <mailto:[EMAIL PROTECTED] > > > > > > > -- > > NOTICE: This e-mail message and all attachments transmitted with it may > contain legally privileged and confidential information intended solely > for the use of the addressee. If the reader of this message is not the > intended recipient, you are hereby notified that any reading, > dissemination, distribution, copying, or other use of this message or > its attachments, hyperlinks, or any other files of any kind is strictly > prohibited. If you have received this message in error, please notify > the sender immediately by telephone (865-218-2000) or by a reply to this > electronic mail message and delete this message and all copies and > backups thereof. > > > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
