|Subject||Re: IN clause - using static values vs table values|
> In my real world app the IN statement has a couple of hundred valuesand the
> query to filter for the values hits the system quite hard, so I wasthat
> concerned that using that query in the IN clause would cause more system
> stress than supplying a string value generated from one execution of
> same query.A couple of hundred is OK, although it hits the index for EACH member.
You will have problems if you try with 1500 though.
> I use the IN clause as part of a DELETE statement and I can't figure
> to use joins to do that, or even if it will be possible at all. Anexample
> would be appreciated.It does not make sense to delete from a join. You can do
delete from sometable where ID in (select ID from sometable join ....)