Skip site navigation (1) Skip section navigation (2)

Re: DatabaseMetaData.getIndexInfo and function-based indexes

From: peter royal <proyal(at)pace2020(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-jdbc(at)postgresql(dot)org, Kris Jurka <books(at)ejurka(dot)com>
Subject: Re: DatabaseMetaData.getIndexInfo and function-based indexes
Date: 2005-02-19 14:02:52
Message-ID: F29E01D5-827E-11D9-8AAF-000A95AC787E@pace2020.com (view raw or flat)
Thread:
Lists: pgsql-jdbc
On Feb 19, 2005, at 12:54 AM, Tom Lane wrote:
> Kris Jurka <books(at)ejurka(dot)com> writes:
>> This is what is actually stored in the pg_attribute table as the 
>> column
>> name for the index.  Determining what the actual expression is would
>> involve decoding the pg_index.indexpr column with pg_get_expr, which 
>> could
>> be done, but then some manual parsing would need to be done to split 
>> this
>> into multiple columns for something like (upper(a), lower(b)).  So the
>> driver can figure this information out, but doesn't presently.
>
> FYI, pg_get_indexdef makes that pretty simple in PG >= 7.4:

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.
-pete

In response to

Responses

pgsql-jdbc by date

Next:From: Sven KöhlerDate: 2005-02-19 17:15:54
Subject: How to get generated primary key?
Previous:From: Tom LaneDate: 2005-02-19 05:54:19
Subject: Re: DatabaseMetaData.getIndexInfo and function-based indexes

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group