Michael/ My attempt to understand and think this through Which Log4j attribute in which Log4j class would support CLOB??? Thanks, Martin
----- Original Message ----- From: "Lutz Michael" <[EMAIL PROTECTED]> To: "'Log4J Users List'" <[EMAIL PROTECTED]> Cc: "Graham Arthur" <[EMAIL PROTECTED]> Sent: Saturday, February 01, 2003 10:30 AM Subject: RE: Using JDBCAppender to insert CLOB? > > > David, > > I don't have the exact answer for you, but what I do know is that CLOB > support is generally database specific, and I know this to be true for > Oracle through JDBC. This is a point one of my colleagues has pointed out > to me as we have looked carefully at Log4j. (without CLOB support, we limit > ourselves to a max length of 4,000 characters per field in Oracle. CLOB's > of course can handle beyond this). > > Time permitting, possibly Art will comment on exactly how to insert CLOB's > into Oracle, but I'm willing to bet the support just isn't there in the > current JDBC appenders (as a possible explanation). Hopefully Art can > comment on the specifics, and someone can subsequently submit a patch, if > it's necessary. > > Mike > > > > -----Original Message----- > From: David Glick [mailto:[EMAIL PROTECTED]] > Sent: Friday, January 31, 2003 7:16 PM > To: Log4J Users List > Subject: Using JDBCAppender to insert CLOB? > > > Does anyone have any advice on how to insert a CLOB into an Oracle table > with > the JDBCAppender? I've been able to insert most other data types, but I'm > totally lost on how to handle this. > > Thanks for any help, > > David Glick > Transmit Consulting, Inc > 619-475-4052 > [EMAIL PROTECTED] > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -------------------------------------------------------------------------- ----- > This message and any included attachments are from Siemens Medical Solutions > Health Services Corporation and are intended only for the addressee(s). > The information contained herein may include trade secrets or privileged or > otherwise confidential information. Unauthorized review, forwarding, printing, > copying, distributing, or using such information is strictly prohibited and may > be unlawful. If you received this message in error, or have reason to believe > you are not authorized to receive it, please promptly delete this message and > notify the sender by e-mail with a copy to [EMAIL PROTECTED] Thank you > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
