| From: | Dmitry Tkach <dmitry(at)openratings(dot)com> |
|---|---|
| To: | Fernando Nasser <fnasser(at)redhat(dot)com> |
| Cc: | Oliver Jowett <oliver(at)opencloud(dot)com>, pgsql-jdbc(at)postgresql(dot)org, Barry Lind <blind(at)xythos(dot)com>, Dave Cramer <Dave(at)micro-automation(dot)net> |
| Subject: | Re: the IN clause saga |
| Date: | 2003-07-22 14:32:05 |
| Message-ID: | 3F1D4AE5.2020504@openratings.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
Fernando Nasser wrote:
> Thanks for summarizing it Oliver.
>
> I've asked Tom Lane about the backend behavior and he informed me that:
>
> 1) 7.4 backends do support parameters in the IN predicate, as ($1, $2,
> $3) (i.e., our (?, ?, ?) syntax).
>
> 2) 7.4 backends have a PostgreSQL specific extension that allows you
> to fill the IN predicate with a list: ($1) (i.e., our (?) ). One has
> to pass a PostgreSQL array, like integer[] to fill the list. Note
> that the parenthesis is already in place, it is not generated by the ?
> expansion.
If I read this correctly, there is no need for any special handling
from the driver side - just setArray() should work. Or am I missing
something?
Dima
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2003-07-22 14:34:34 | Re: the IN clause saga |
| Previous Message | Dmitry Tkach | 2003-07-22 14:30:09 | Re: the IN clause saga |