| From: | Oliver Jowett <oliver(at)opencloud(dot)com> |
|---|---|
| To: | Dave Cramer <pg(at)fastcrypt(dot)com> |
| Cc: | List <pgsql-jdbc(at)postgresql(dot)org> |
| Subject: | Re: jdbc cts final diff for review |
| Date: | 2005-07-01 00:56:09 |
| Message-ID: | 42C494A9.4000505@opencloud.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Dave Cramer wrote:
> Did you read my reasons for the ugly if double, then float stuff ?
Haven't had time to get my head around that yet.. can you translate it
to an explanation of something in the JDBC spec that we don't do
correctly? It's a bit hard to understand what's going wrong without the
CTS code to hand..
> I think it can be removed, however I think sooner than later we will be
> dealing
> with more complex parameters when stored procedures with real IN/OUT parms
Well, let's add the complexity only when we need it..
>> I still think they are redundant and should be entirely removed. We can
>> do that afterwards though.
>
> If absolutely necessary, however I don't think setObject with a
> different type is
> in the critical path
I'll hack on it if I have time after this is all applied; don't worry
about it for now since it's already in HEAD.
>> Why the repackaging?
>
> can't remember now.
Can you avoid repackaging then? Less CVS churn..
-O
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nidhi Srivastava | 2005-07-01 08:30:53 | Create Database using JDBC |
| Previous Message | Dave Cramer | 2005-07-01 00:51:02 | Re: jdbc cts final diff for review |