| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Mark Kirkwood <mark(dot)kirkwood(at)catalyst(dot)net(dot)nz> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: JDBC index metadata filter_condition |
| Date: | 2009-12-04 21:24:49 |
| Message-ID: | alpine.BSO.2.00.0912041622450.4678@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Wed, 2 Dec 2009, Mark Kirkwood wrote:
> I'm investigating a Java based schema designer tool which uses the JDBC
> metadata API for most of its information gathering. I notice that the
> filter_condition field returned in the getIndexInfo() method's resultset is
> always null. It seems straightforward to fix this (see attached patch)
>
Applied to CVS for 8.4 and 8.5. It's half new feature, half bugfix, so I
didn't backpatch it all the way.
> I've specified 7.4 as the earliest server version that will try to populate
> this field - even tho it looks like 7.3 might work (do we care about 7.3 and
> earlier?)
>
Since 7.4 is the oldest officially supported version, I guess that's our
cutoff. I still test back to 7.2, so I adjusted the patch to make it work
that far back.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Kellerer | 2009-12-08 08:56:45 | Version information inside the driver's jar file |
| Previous Message | Kris Jurka | 2009-12-04 19:55:17 | Re: COPY and turning off autocommit |