Re: ANY subquery and PreparedStatements - Mailing list pgsql-jdbc

From David Wall
Subject Re: ANY subquery and PreparedStatements
Date
Msg-id 001e01c2d842$7bed8500$3201a8c0@expertrade.com
Whole thread Raw
In response to ANY subquery and PreparedStatements  (Felipe Schnack <felipes@ritterdosreis.br>)
Responses Re: ANY subquery and PreparedStatements  (Felipe Schnack <felipes@ritterdosreis.br>)
Re: ANY subquery and PreparedStatements  (Csaba Nagy <nagy@ecircle-ag.com>)
List pgsql-jdbc
>   You're right... but it's actually based on user interaction (i.e.:
> selecting items using checkboxes)
>   I guess I'll just have to issue a query per item... ugly :-(

Why can't you simply build the prepared statement on the fly based on the
number of values to be placed in the IN list?  If you have 3 items, you just
append three '?' and if you have 20 items, then you append 20 '?' to your
list.  This way the number of '?' will match the number of
PreparedStatement.setXXX() calls and you don't have to rely on the database
handling all the nulls.  Since the list is fairly dynamic anyway, it's
overall performance will be about the same (and it's much better than doing
a series of queries instead).

Of course, there are limits on how long a query can be for most databases,
so you may find that if the list is too long, you'll run into query
processor problems.

David


pgsql-jdbc by date:

Previous
From: "Dirk Bromberg"
Date:
Subject: Priority of Statments / Connections
Next
From: "Nagy Istvan"
Date:
Subject: Re: SSL for JDBC