For what it's worth, I think Derby is "in the wrong" here by claiming "exception" as a reserved keyword in their SQL. It wouldn't bother me if you reverted back to "EXCEPTION." I'd hate to break a bunch of CustomDBReceiver installations for my minor issue.
At any rate, thanks for the support! On 8/16/07, Scott Deboy < [EMAIL PROTECTED]> wrote: > > I've committed this change - the new column name is THROWABLE. > > Thanks > > Scott > > -----Original Message----- > From: Scott Deboy [mailto:[EMAIL PROTECTED] > Sent: Wed 8/15/2007 9:52 PM > To: Log4J Users List [EMAIL PROTECTED] > Subject: RE: Chainsaw CustomDBReceiver -- "EXCEPTION" is reserved keyword > in Apache Derby SQL > > We could change the name of the column representing the exception to > THROWABLE. > > Folks who already have a CustomSQLDBReceiver configuration would be > broken, but since it's only been available through log4j 1.3, that's > probably not a big issue. > > One other option is to allow any of the column names to be aliases through > the config file, but that's probably not worth the work. > > > Scott Deboy > COMOTIV SYSTEMS > 111 SW Columbia Street Ste. 950 > Portland, OR 97201 > > Telephone: 503.224.7496 > Cell: 503.997.1367 > Fax: 503.222.0185 > > [EMAIL PROTECTED] > > www.comotivsystems.com > > > > -----Original Message----- > From: Adam Mitchell [mailto:[EMAIL PROTECTED] ] > Sent: Fri 8/3/2007 12:58 PM > To: [email protected] > Subject: Chainsaw CustomDBReceiver -- "EXCEPTION" is reserved keyword in > Apache Derby SQL > > Is there a way to remap the column names that CustomDBReceiver expects > back > from the DB? I'm testing on Apache Derby and, apparently, "EXCEPTION" is > a > reserved keyword in Derby SQL. But CustomDBReceiver logs an error if that > > column is missing. > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
