X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.2])
	by svr1.postgresql.org (Postfix) with ESMTP
	id D48DBD1B16D; Tue, 25 May 2004 04:29:48 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024)
	with ESMTP id 00216-06; Tue, 25 May 2004 04:29:28 -0300 (ADT)
Received: from anchor-post-37.mail.demon.net (anchor-post-36.mail.demon.net
	[194.217.242.86]) by svr1.postgresql.org (Postfix) with ESMTP
	id 6EEB4D1B459; Tue, 25 May 2004 04:29:25 -0300 (ADT)
Received: from mailgate.vale-housing.co.uk ([80.176.1.146]
	helo=salem.vale-housing.co.uk)
	by anchor-post-37.mail.demon.net with esmtp (Exim 3.35 #1)
	id 1BSWNJ-000Mjf-0b; Tue, 25 May 2004 08:29:26 +0100
Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: [webmaster] Problem with 'report a bug form'
X-MimeOLE: Produced By Microsoft Exchange V6.0.6249.0
Date: Tue, 25 May 2004 08:29:25 +0100
Message-ID: <03AF4E498C591348A42FC93DEA9661B889FEA1@mail.vale-housing.co.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [webmaster] Problem with 'report a bug form'
thread-index: AcRBYuS+HDa5pzVaRRuwz/zOKpBvdwAxuGog
From: "Dave Page" <dpage@vale-housing.co.uk>
To: <pgsql-www@postgresql.org>
Cc: "David Brownlee" <abs@absd.org>, <webmaster@postgresql.org>
X-Virus-Scanned: by amavisd-new at postgresql.org
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=
X-Spam-Level: 
X-Archive-Number: 200405/97
X-Sequence-Number: 4476

Can someone take a look at this problem reported by David please (the
bug form that is, not the JDBC issue)? I'm pretty swamped right now :-(

Regards, Dave.

> -----Original Message-----
> From: David Brownlee [mailto:abs@absd.org]=20
> Sent: 22 May 2004 18:15
> To: webmaster@postgresql.org
> Subject: [webmaster] Problem with 'report a bug form'
>=20
>  	Submit does not appear to work:
>=20
>  	Contents were:
>=20
>=20
> In AbstractJdbc2ResultSet:parseQuery can end up leaving a ;=20
> on the end of a tablename, which when later used in=20
> isUpdateable() will choke.
> The following 'fixes' it:
>=20
> --- org/postgresql/jdbc2/AbstractJdbc2ResultSet.java.orig=20=20=20=20=20
>   2004-05-21=20
> 12:54
> :29.000000000 +0100
> +++ org/postgresql/jdbc2/AbstractJdbc2ResultSet.java
> @@ -1448,7 +1450,7 @@ public abstract class AbstractJdbc2Resul
>                          {
>                                  if=20
> (name.toLowerCase().equals("from"))
>                                  {
> -                                       tableName =3D st.nextToken();
> +                                       tableName =3D
> st.nextToken().replaceAll(";
> ", "");
>                                          tableFound =3D true;
>                                  }
>=20
> This was found while writing a small java tool to copy the=20
> contents of one database to another, which can be provided to=20
> demonstrate the problem on request. Would have attached it=20
> here if there had been an option :)
>=20
> --=20
>  			   David Brownlee -- abs@absd.org
>=20
> ---------------------------(end of=20
> broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to=20
> majordomo@postgresql.org
>=20