Re: Bug in getImportedExportedKeys(), DatabaseMetaData class

From: Kris Jurka <books(at)ejurka(dot)com>
To: Todd Cornett <tcornett(at)mitre(dot)org>
Cc: <pgsql-jdbc(at)postgresql(dot)org>, "Hoyt,Jeffrey C(dot)" <jchoyt(at)mitre(dot)org>, "Smith,Kenneth P(dot)" <kps(at)mitre(dot)org>, "Carley,Monica P(dot)" <mcarley(at)mitre(dot)org>
Subject: Re: Bug in getImportedExportedKeys(), DatabaseMetaData class
Date: 2003-04-16 07:24:02
Message-ID: Pine.LNX.4.33.0304160320410.5589-200000@leary.csoft.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

On Tue, 8 Apr 2003, Todd Cornett wrote:

> All:
>
> We found that the current use of the StringTokenizer to parse out the
> response from the database acheieves the desired result only when the
> returning column and table names do not contain either '\' or '0'.

The attached patch fixes this for all JDK versions by using its own
tokenizing routine.

Kris Jurka

Attachment Content-Type Size
fktokenizer.patch text/plain 2.9 KB

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Kris Jurka 2003-04-16 07:25:47 Re: DatabaseMetaData.getCrossReference(...)
Previous Message Kris Jurka 2003-04-16 07:20:24 Re: Index metadata not sorted by ORDINAL_POSITION