Re: DatabaseMetaData.getIndexInfo and function-based indexes - Mailing list pgsql-jdbc

From peter royal
Subject Re: DatabaseMetaData.getIndexInfo and function-based indexes
Date
Msg-id 46E72C0A-85C1-11D9-8AAF-000A95AC787E@pace2020.com
Whole thread Raw
In response to Re: DatabaseMetaData.getIndexInfo and function-based indexes  (Kris Jurka <books@ejurka.com>)
Responses Re: DatabaseMetaData.getIndexInfo and function-based indexes
Re: DatabaseMetaData.getIndexInfo and function-based indexes
List pgsql-jdbc
On Feb 19, 2005, at 2:27 PM, Kris Jurka wrote:
> On Sat, 19 Feb 2005, peter royal wrote:
>
>> i'm mainly concerned about single-column functional indexes right now.
>> being able to get upper(a) as the column name would be enough now. but
>> tom's method for working with multi-column functional indices would be
>> a bonus too.
>>
>> would a patch to have DMD.getIndexInfo() return this information be
>> accepted into the tree? if so, i'll work one up.
>
>
> Yes, a column name of "pg_expression_N" is rather useless.  upper(a)
> may
> not be a column name, but it is more accurate and informative.

Patch + test cases attached.
-pete


Attachment

pgsql-jdbc by date:

Previous
From: Guillaume Cottenceau
Date:
Subject: PGStatement#setUseServerPrepare breaking PreparedStatement#executeUpdate return value?
Next
From: Markus Schaber
Date:
Subject: Re: [postgis-devel] JDBC & WKB - 400% overhead