Re: DBI placeholders less efficient?

Placeholder code is primarily more maintainable and more secure, which is why it's used. It's more efficient if the server or the DBD can take advantage of not having to parse the same statement over and over. Oracle 9.2 definitely has this feature.

You might want to consider doing the following (in no particular order)

Turn on DBI's debug feature, which will tell you exactly what SQL is being executed.
It looks like you're using integers or some other numeric type. You might need to explicitly tell DBD::Oracle with the bind_param() method exactly what type it is. That way it won't be quoting your number which does bad things to your optimizer.

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

Comment on Re: DBI placeholders less efficient?