Re: What's the best alternative to this pl/sql ?

damorgan_at_exesolutions.com said...
(snip)
>
> If the source of the SQL is some front-end I'd advise against putting any SQL
> there at all ... compiled, prepared, or otherwise. Passing SQL statements across
> a wire is not an efficient use of resources.
>
> Daniel Morgan
>

I agree with you 100% ... in principle, at least. However, if I wrote a stored procedure (or even if I put them all in a single package) for every one of the hundreds (thousands?) of source SQL we're passing from our Java apps to the db, I'd have to get very creative with the procedure names - Get<colnames>, Get<colnames>_When_Sorting_<colname>, Get<colnames>_When_Joining_With_<tablename>, and so on.

Is it ok if I act as a name-dropper? Paraphrasing what Tom Kyte said, they should never have added the Statement to the JDBC spec; only allowed PreparedStatement.

-- 
/Karsten
DBA > retired > DBA