| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| Cc: | Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: getIndexInfo() not returning operator classes |
| Date: | 2005-11-10 19:18:21 |
| Message-ID: | 11082.1131650301@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Kris Jurka <books(at)ejurka(dot)com> writes:
> In the function case the indexed data is not the column data, so putting
> the column's name is misleading.
There's another argument here, which is that the JDBC spec (presumably)
says that that field is a column name, full stop. Now an app that's
using functional indexes is already outside the spec, so returning
something that's not just a name seems acceptable in that case, and
arguably it's the proper name for the index's data anyway. But cramming
an opclass name in there seems to me to violate the spirit of the spec.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2005-11-10 20:34:10 | Re: Getting param names |
| Previous Message | Thomas Kellerer | 2005-11-10 19:06:14 | Re: getIndexInfo() not returning operator classes |