Return-Path: Delivered-To: apmail-ibatis-user-java-archive@www.apache.org Received: (qmail 55789 invoked from network); 2 Feb 2006 14:22:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 2 Feb 2006 14:22:51 -0000 Received: (qmail 10163 invoked by uid 500); 2 Feb 2006 14:22:50 -0000 Delivered-To: apmail-ibatis-user-java-archive@ibatis.apache.org Received: (qmail 9995 invoked by uid 500); 2 Feb 2006 14:22:48 -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 9984 invoked by uid 99); 2 Feb 2006 14:22:48 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 06:22:48 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [72.36.192.138] (HELO MAIL3.plesklogin.net) (72.36.192.138) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Feb 2006 06:22:47 -0800 Received: from [192.168.0.9] ([81.178.173.168]) by plesklogin.net with MailEnable ESMTP; Thu, 02 Feb 2006 14:22:05 +0000 Message-ID: <43E2158D.7030906@last.fm> Date: Thu, 02 Feb 2006 14:22:05 +0000 From: Johan Oskarsson User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Accept-Language: en-us, en MIME-Version: 1.0 To: user-java@ibatis.apache.org X-PXPME-Bayesian: 68|45|0.008564|0.097022|0.000000 X-PXPME-VirusCheck: Clean Subject: Re: Invalid character References: <43E202E1.90809@oskarsson.nu> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Larry Meadors wrote: >This is an issue in the JDBC driver, not iBATIS. > >I'd suggest deleting the row with one of the native DB toosl that come >with postresql, or setting the field's value to null or "". > >Larry > > Yes, I realize that the exception/problem is caused by the jdbc driver, however I'd like to let the query finish somehow, like I could when I retrieved the rows manually using jdbc by catching the exceptions for the resultset.get and just moving on to the next row if something went wrong. I haven't found any way to do this using ibatis. I could remove the problematic row in the db, but as new ones are added by users the problem could resurface. /Johan