Return-Path: Delivered-To: apmail-db-ojb-dev-archive@www.apache.org Received: (qmail 37297 invoked from network); 20 Jun 2004 12:36:32 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 20 Jun 2004 12:36:32 -0000 Received: (qmail 10360 invoked by uid 500); 20 Jun 2004 12:36:29 -0000 Delivered-To: apmail-db-ojb-dev-archive@db.apache.org Received: (qmail 10316 invoked by uid 500); 20 Jun 2004 12:36:29 -0000 Mailing-List: contact ojb-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "OJB Developers List" Reply-To: "OJB Developers List" Delivered-To: mailing list ojb-dev@db.apache.org Received: (qmail 10301 invoked by uid 99); 20 Jun 2004 12:36:29 -0000 Received: from [66.199.152.34] (HELO kgb07.kgbinternet.com) (66.199.152.34) by apache.org (qpsmtpd/0.27.1) with ESMTP; Sun, 20 Jun 2004 05:36:29 -0700 Received: from [192.168.1.100] (pool-138-88-29-3.res.east.verizon.net [138.88.29.3]) (authenticated bits=0) by kgb07.kgbinternet.com (8.12.8/8.12.8) with ESMTP id i5KCaPcF002285 for ; Sun, 20 Jun 2004 06:36:25 -0600 User-Agent: Microsoft-Entourage/11.0.0.040405 Date: Sun, 20 Jun 2004 08:36:41 -0400 Subject: Re: Postgres escaping issues From: "Robert S. Sfeir" To: OJB Developers List Message-ID: In-Reply-To: <40D583C5.1000507@first.fhg.de> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N I've been searching the mailing list, and by all accounts on there this should work, but it does, even in psql. I am checking with different characters, the select behavior is just not consistent. See my second post. The escaping works, it just doesn't work consistently... Still looking. This is very bizarre. R On 6/20/04 8:32 AM, "Thomas Dudziak" wrote: > Robert, could you also run test with a different escape character ? > Also, have you checked the postgresql mailing list ? Perhaps this is a > known behavior with a workaround that we can use. I'd prefer we delay > the release for a day or two if we can fix this in an easy way (eg. > without changing OJB too much) > > Tom > > --------------------------------------------------------------------- > To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org > For additional commands, e-mail: ojb-dev-help@db.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: ojb-dev-unsubscribe@db.apache.org For additional commands, e-mail: ojb-dev-help@db.apache.org