Re: ANY subquery and PreparedStatements

From: Csaba Nagy <nagy(at)ecircle-ag(dot)com>
To: Felipe Schnack <felipes(at)ritterdosreis(dot)br>
Cc: pgsql-jdbc <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: ANY subquery and PreparedStatements
Date: 2003-02-19 16:54:45
Message-ID: 1045673685.28237.11.camel@coppola.ecircle.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Hi Felipe,

What we are doing in our code is to prepare a statement with a lot of
parameter placeholders, something like:

select * from <table> where <field> in (?,?,?,?,?,?,?,?,?,?,?,?,?,?,?);

and then set some of the parameters with the available values, and set
the rest to nulls. The nulls should be disregarded by the backend
anyway... this works well with Oracle, I'm not sure how efficient is
with Postgres.
The only reason to use this is to have a prepared statement instead of
building dynamic queries all the time. You only must make sure the nr.
of ? signs is at least as much as many parameters you can have at
maximum.

HTH,
Csaba.

On Wed, 2003-02-19 at 13:24, Felipe Schnack wrote:
> I'm afraid it kind of impossible to use PreparedStatements with the
> "ANY" subquery keyword... For example, if I take this query and prepare
> it:
> "select * from <table> where <field> any (?)"
> How can I set my parameter as a list of values, so my query searches
> for for different values of the specified field?
>
> --
>
> Felipe Schnack
> Analista de Sistemas
> felipes(at)ritterdosreis(dot)br
> Cel.: (51)91287530
> Linux Counter #281893
>
> Centro Universitário Ritter dos Reis
> http://www.ritterdosreis.br
> ritter(at)ritterdosreis(dot)br
> Fone/Fax.: (51)32303341
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Felipe Schnack 2003-02-19 16:57:03 Re: ANY subquery and PreparedStatements
Previous Message Mykola Dudar 2003-02-19 16:44:26 exception in decodeUTF8