| From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
|---|---|
| To: | List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | patch for passing the cts |
| Date: | 2005-06-14 15:20:08 |
| Message-ID: | 2BC23AE7-6381-41BA-AE89-CC81D1C932A7@fastcrypt.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Well the good news is that the driver and the backend will pass the
cts with this patch.
Rather than commit this as is, I'd like to discuss the patch as it is.
I'm really not happy with the handling of IN/OUT parameters in the
query executor, however deferring parsing doesn't seem to be an
option either.
We need to know how many parameters there are before
CallableStatment.setXXX, and CallableStatement.registerOutParameter
are called.
The real solution is to extend the FE/BE protocol to specify IN/OUT
parameters and send them down the wire.
| Attachment | Content-Type | Size |
|---|---|---|
| callable.diff.gz | application/x-gzip | 17.8 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roland Walter | 2005-06-14 15:38:32 | Re: Any example code of using passwords with JDBC? |
| Previous Message | Dave Cramer | 2005-06-14 15:14:47 | Re: Any example code of using passwords with JDBC? |