| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Kris Jurka <books(at)ejurka(dot)com> |
| Cc: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: Wrong column names in ResultSetMetaData |
| Date: | 2004-07-29 09:27:13 |
| Message-ID: | 4108C2F1.7090805@opencloud.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Kris Jurka wrote:
> This was done intentionally. Back in January I applied this patch:
>
> date: 2004/01/13 03:07:09; author: jurka; state: Exp; lines: +95 -31
> This patch is the culmination of Jan-Andre le Roux's work on enhancing
> the ResultSetMetaData methods with new information available in the V3
> protocol. He wandered off of the verge of completing it and I've just
> done some minor reworking and editing.
>
> This implements getSchemaName, getTableName, getColumnName,
> getColumnLabel, and isNullable.
I notice that the implementation of updateable resultsets use
Field.getColumnLabel() when generating the UPDATE/SELECT/etc SQL.
Presumably this should be using Field.getColumnName() given the current
semantics?
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremiah Jahn | 2004-07-29 17:38:12 | PreparedStatement.getMetaData() and Creator |
| Previous Message | Kris Jurka | 2004-07-29 03:51:13 | Re: Wrong column names in ResultSetMetaData |