| From: | peter royal <proyal(at)pace2020(dot)com> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: DatabaseMetaData.getIndexInfo and function-based indexes |
| Date: | 2005-02-23 17:35:14 |
| Message-ID: | 46E72C0A-85C1-11D9-8AAF-000A95AC787E@pace2020.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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 | Content-Type | Size |
|---|---|---|
| getFunctionalIndices.patch | application/octet-stream | 4.5 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Markus Schaber | 2005-02-23 17:35:30 | Re: [postgis-devel] JDBC & WKB - 400% overhead |
| Previous Message | dblasby | 2005-02-23 17:25:01 | Re: [postgis-devel] JDBC & WKB - 400% overhead |