RE: Chainsaw with CustomSQLDBReceiver fo oracle

2005-03-22 Thread Scott Deboy
ver config, change IDField to reference the ID column (unless it's really the msisdn column you're using as the unique id), and get rid of the 'application' and 'hostname' params (they're defined in the sql concat statement above) -Original Message-

RE: Chainsaw with CustomSQLDBReceiver fo oracle

2005-03-22 Thread Ghielli Patrick
e.org/log4j/"; debug="true"> -Original Message- From: Scott Deboy [mailto:[EMAIL PROTECTED] Sent: vrijdag 18 maart 2005 6:22 To: Log4J

RE: Chainsaw with CustomSQLDBReceiver fo oracle

2005-03-22 Thread Ghielli Patrick
l. Regards, Patrick. -Original Message- From: Scott Deboy [mailto:[EMAIL PROTECTED] Sent: vrijdag 18 maart 2005 6:22 To: Log4J Users List Subject: RE: Chainsaw with CustomSQLDBReceiver fo oracle If you can post your table schema and what you have for an 'sql' parameter and we can fi

RE: Chainsaw with CustomSQLDBReceiver fo oracle

2005-03-17 Thread Scott Deboy
If you can post your table schema and what you have for an 'sql' parameter and we can figure it out. Scott There are a number of limitations described in the JavaDoc: http://cvs.apache.org/viewcvs.cgi/logging-log4j/src/java/org/apache/log4j/db/CustomSQLDBReceiver.java?rev=1.3&view=markup - You