Hello Michael- Here is an example of setting the Oracle PreparedStatement's Clob http://otn.oracle.com/sample_code/tech/java/sqlj_jdbc/files/9i_jdbc/NewLOBAP ISample/NewLOBAPISample.java.html Now how do we package this within JDBCAppender.. I have requested Danko Mannhaupt to help with this scenario as he has experience with JDBCAppender In any case we should soon have our answer Many Thanks, -Martin
----- Original Message ----- From: "Lutz Michael" <[EMAIL PROTECTED]> To: "'Martin'" <[EMAIL PROTECTED]>; "Log4J Users List" <[EMAIL PROTECTED]> Cc: "Graham Arthur" <[EMAIL PROTECTED]> Sent: Saturday, February 01, 2003 1:03 PM Subject: RE: Using JDBCAppender to insert CLOB? > > > Good question. > > I'm getting out of my comfort level here, because I don't know the specifics > about CLOB's, but I'll offer up all that I believe to be correct. > > Last week, I showed my colleague the SQL typically found in a Log4j config > file for a JDBC setup (e.g. log4j.appender.myJDBC.Sql="INSERT INTO > table_name_here VALUES ..."), and he replied, "that SQL statement won't work > in Oracle if any of the fields are CLOB's." Thus, I'm guessing that > possibly the fix could be made in the config file directly on the SQL; > however, I suspect there's more to it than that. He indicated it was > somewhat complex. > > Unfortunately, Art's out today (Saturday), but he does understand CLOB > support clearly (across RDBMS systems). If the question is not answered by > Monday, I'll track him down and summarize from an Oracle perspective what > needs to be done. Then the Log4j pros can determine the best approach, > although I'm hoping it's just a SQL change in the config file, we'll see. > > I'm not familiar with the details of the Log4j JDBC appenders. I just > wanted to offer up the fact that CLOB support is not consistent across > RDBMS's even if one is going through JDBC. > > I apologize for not having a crystal clear answer. > > > -----Original Message----- > From: Martin [mailto:[EMAIL PROTECTED]] > Sent: Monday, September 02, 2002 9:23 AM > To: Log4J Users List > Cc: Lutz Michael > Subject: Re: Using JDBCAppender to insert CLOB? > > > 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] > > > > -------------------------------------------------------------------------- ----- > 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]
