Re: IN clauses via setObject(Collection) [Was: Re: Prepared

From: Dmitry Tkach <dmitry(at)openratings(dot)com>
To: Oliver Jowett <oliver(at)opencloud(dot)com>
Cc: Fernando Nasser <fnasser(at)redhat(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: IN clauses via setObject(Collection) [Was: Re: Prepared
Date: 2003-07-21 16:33:40
Message-ID: 3F1C15E4.5080702@openratings.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

>
>
>Also.. what would we do with this object?
>
>public class AnnoyingObject implements java.util.Collection, java.sql.Array {
> // ...
>}
>
>then setObject(n, new AnnoyingObject(), Types.ARRAY);
>
>Is that an Array, or an IN clause of Arrays? :)
>
>(Array is the obvious candidate for also being a Collection, but potentially
>you could do it with other types too)
>
>
>
java.sql.Array is an ARRAY.
I don't think there is any ambiguity here, as it is the only reason I
can imagine for somebody to implement a sql.Array is to pass an ARRAY
into a PreparedStatement.

If they wanted a set of arrays, they would have to pass in a Collection,
containing java.sql.Arrays as elements...

Dima

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Darin Ohashi 2003-07-21 16:38:42 Re: IN clauses via setObject(Collection) [Was: Re: Prepare
Previous Message Dmitry Tkach 2003-07-21 16:29:12 Re: Prepared Statements