| From: | Dmitry Tkach <dmitry(at)openratings(dot)com> |
|---|---|
| To: | Fernando Nasser <fnasser(at)redhat(dot)com> |
| Cc: | Oliver Jowett <oliver(at)opencloud(dot)com>, Kim Ho <kho(at)redhat(dot)com>, Barry Lind <blind(at)xythos(dot)com>, pgsql-jdbc-list <pgsql-jdbc(at)postgresql(dot)org>, Dave Cramer <Dave(at)micro-automation(dot)net> |
| Subject: | Re: Prepared Statements |
| Date: | 2003-07-21 14:46:40 |
| Message-ID: | 3F1BFCD0.80507@openratings.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
>
>
>>>
>> Why not just allow setObject() to take Collection as an argument?
>> You would not need any special implementations then... and the
>> application would not need to waste cycles on wrapping/unwrapping
>> those Arrays every time...
>>
>
> That is an interesting idea. But how do we know the type of the
> elements that should go in the list? We will just get java.Objects as
> we go through the Collection.
>
>
You can require the 'type' argument to setObject() to specify the target
type.
Besides, knowing the exact type doesn't really matter much, because you
aare going to be quoting everything anyways :-)
Dima
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Kovacs | 2003-07-21 14:48:53 | Re: Prepared Statements |
| Previous Message | Oliver Jowett | 2003-07-21 14:44:28 | Re: Prepared Statements |