Prepared Statement with SQL 'IN' Clause

Question

Hi,
I am trying to write a JDBC SQL call to a database using a prepared statement, the call looks something like:
select *
from table
where field in (?, ? ,?)
this thing is that i don't know how many 'IN' parameters are needed until runtime (they come from a List), so is there an easy way of dealing with this, I haven't been able to find any information on this problem anywhere?

Answer 1

>
Hmmm...more expensive than say doing a query on on 2 billion rows with no index?
More expensive than doing a cross server join?
More expensive than doing a restore?
I knew that someone would point this out. :)
I just tried to exaggerate the importance of cursor sharing. This is one of the most important topic in DBMS world, but quite often ignored by JAVA world. I hope that you understand my good intention.
>
2. Insert data corresponding to bind variable to "T". Interesting idea. Please provide the algorithm for that. The only ones I can come up with
1. Involved creating a "dynamic" SQL for the insert
2. Doing multiple cross network inserts.
The first of course is exactly what you said your solution prevented. The second will be more expensive than sending a single dynamically created select.Hopefully, this is not just an "interesting" idea, but very common technique in DBMS. Actually one of the common techniques. There are couple of ways to handle this kind(variable number of bind variables in "IN" clause) of problem.
What i commented was that the simplest one. It's like this:
(based on Oracle)
SQL> create global temporary table bind_temp(value int);
PreparedStatement stmt = con.prepareStatement("INSERT INTO bid_temp VALUES(?)");
for(...) {
     stmt.setInt(1, aValue)
     stmt.addBatch();
stmt.executeBatch();
Statement stmt2 = con.executeQuery("SELECT * FROM target_table WHERE id IN (bind_temp)");
...Doesn't it look pretty? Pretty for both Java developers and DBAs.
By virtue of the mechanism of batch processing, the total DBMS call is just twice and you need just 2 completely sharable SQL statements.
(Hopefully you might understand that Oracle global temporary table is just session scope and we don't need them to be stored permanently)
Above pattern is quite beneficial than these pattern of queries.
SELECT * FROM target_table WHERE id IN (?)
SELECT * FROM target_table WHERE id IN (?,?)
SELECT * FROM target_table WHERE id IN (?,?,?)
SELECT * FROM target_table WHERE id IN (?,?,?,?,.......,?)
If you have large quantity of above patterns of queries, you should note that there are another bunch of better techniques. I noted just one of them.
Hope this clairfies my point.