Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 523 invoked from network); 23 Mar 2007 12:04:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Mar 2007 12:04:44 -0000 Received: (qmail 70027 invoked by uid 500); 23 Mar 2007 12:04:49 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 70017 invoked by uid 500); 23 Mar 2007 12:04:49 -0000 Mailing-List: contact user-java-help@ibatis.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user-java@ibatis.apache.org Delivered-To: mailing list user-java@ibatis.apache.org Received: (qmail 70006 invoked by uid 99); 23 Mar 2007 12:04:49 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Mar 2007 05:04:49 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [207.54.49.43] (HELO us-atl-mx02.infor.com) (207.54.49.43) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Mar 2007 05:04:39 -0700 Received: from us-atl-mx03.infor.com ([10.32.3.33]) by us-atl-mx02.infor.com with Microsoft SMTPSVC(6.0.3790.1830); Fri, 23 Mar 2007 08:04:18 -0400 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Logging SQL statements Date: Fri, 23 Mar 2007 08:04:17 -0400 Message-ID: In-Reply-To: <9632994.post@talk.nabble.com> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Logging SQL statements Thread-Index: AcdtP5h+Q/xyWRWkRGebB690RolYJAAA0Mhw References: <9632495.post@talk.nabble.com> <9632994.post@talk.nabble.com> From: "Murtaza Goga" To: X-OriginalArrivalTime: 23 Mar 2007 12:04:18.0378 (UTC) FILETIME=[625BFAA0:01C76D43] X-Virus-Checked: Checked by ClamAV on apache.org It would. =20 You could extend the FileAppender in Log4J and filter out the selects. Not as elegant but it would work. -----Original Message----- From: K1RUHA [mailto:kiryl_kazakevich@yahoo.com]=20 Sent: Friday, March 23, 2007 7:37 AM To: user-java@ibatis.apache.org Subject: RE: Logging SQL statements But this approach will also generate log messages for SELECT statements. I was thinking about getting sql statements in DAO and then log them depending on configuration parameter. Goga, Murtaza wrote: >=20 > If you are using Log4J, you can add an appender and route the logged sql > activity from iBatis into a separate file. The category I believe is > "java.sql."=20 >=20 > =20 >=20 > ________________________________ >=20 > From: K1RUHA [mailto:kiryl_kazakevich@yahoo.com]=20 > Sent: Friday, March 23, 2007 6:59 AM > To: user-java@ibatis.apache.org > Subject: Logging SQL statements >=20 > =20 >=20 > Hello. I'd like to use iBATIS in our project, but I have one requierent, > that I don't know if it supports. I need to log SQL statements that > modify database (UPDATE and DELETE) into separate file. So I need some > approach to get these statements in my Java code. Would you mind tell me > if iBATIS can do this? Thanx, Kiryl=20 >=20 > ________________________________ >=20 > View this message in context: Logging SQL statements > > Sent from the iBATIS - User - Java mailing list archive > at Nabble.com. >=20 >=20 >=20 --=20 View this message in context: http://www.nabble.com/Logging-SQL-statements-tf3453072.html#a9632994 Sent from the iBATIS - User - Java mailing list archive at Nabble.com.