| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Thor Michael Støre <thormichael(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: java.sql.DatabaseMetaData.getProcedures and overloaded functions |
| Date: | 2011-01-03 19:23:00 |
| Message-ID: | alpine.BSO.2.00.1101031421480.19191@leary.csoft.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Sun, 2 Jan 2011, Thor Michael St?re wrote:
> Also, I see SPECIFIC_NAME was added to JDBC 4, so I imagine that to
> correctly add it one would override getProcedures and
> getProcedureColumns in
> org.postgresql.jdbc4.AbstractJdbc4DatabaseMetaData and have them return
> the additional column(s). I took a look at the code and it seem straight
> forward enough for getProcedures, but getProcedureColumns has six other
> new columns as well and seems a bit hairier so I'm not sure if should
> throw myself over adding this.
>
I've checked in a fix for this to CVS so that getProcedures and
getProcedureColumns have all of the columns defined in JDBC4 including
SPECIFIC_NAME.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thor Michael Støre | 2011-01-03 21:53:47 | Re: java.sql.DatabaseMetaData.getProcedures and overloaded functions |
| Previous Message | Thor Michael Støre | 2011-01-02 20:47:07 | Re: java.sql.DatabaseMetaData.getProcedures and overloaded functions |