| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | peter royal <proyal(at)pace2020(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-03-04 06:55:59 |
| Message-ID: | Pine.BSO.4.56.0503040152260.6222@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Wed, 23 Feb 2005, peter royal wrote:
> >> 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.
I've applied this with some minor modifications:
- I've extended it to work for < 7.4 servers
- You had modified the SELECT column order to return COLUMN_NAME in
a different position than required by the spec.
- Fixed the test cases to pass for < 7.4 servers
Thanks.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergio Lob | 2005-03-04 13:58:20 | Re: BUG #1523: precision column value returned from getTypeInfo() |
| Previous Message | Kris Jurka | 2005-03-04 03:06:54 | Re: BUG #1523: precision column value returned from getTypeInfo() |