Received: from candle.pha.pa.us (candle.navpoint.com [162.33.245.46]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f5UIZJa59039 for ; Sat, 30 Jun 2001 14:35:19 -0400 (EDT) (envelope-from pgman@candle.pha.pa.us) Received: (from pgman@localhost) by candle.pha.pa.us (8.10.1/8.10.1) id f5UIZBG19403; Sat, 30 Jun 2001 14:35:11 -0400 (EDT) From: Bruce Momjian Message-Id: <200106301835.f5UIZBG19403@candle.pha.pa.us> Subject: Re: Re: [INTERFACES] New code for JDBC driver In-Reply-To: <005301c10191$8ae2ce50$0201a8c0@inspiron> "from Dave Cramer at Jun 30, 2001 02:21:54 pm" To: Dave Cramer Date: Sat, 30 Jun 2001 14:35:11 -0400 (EDT) CC: Arsalan Zaidi , PostgreSQL jdbc list X-Mailer: ELM [version 2.4ME+ PL90 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Archive-Number: 200106/172 X-Sequence-Number: 920 > Can you give us some background. What is this trying to solve? > >From the look of it the purpose is to remove embedded semicolons and quotes. > >From my POV this should be handled by the backend. > > My reasons are as follows: > > 1) Any attempt at parsing the query by the driver will slow the driver down. > 2) If the purpose of parsing is to make an incorrect query correct; then I > would prefer the backend fail and make me fix my code. psql does this kind of query spliting but for different reasons. -- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania 19026