April 3rd, 2017, 06:48 AM
Downsides using DB operations on stored procedures
I started working on a project where some Firebird databases are in use. When I was doing my first few things in the new program I used an existing stored procedure but needed some filtered data from the resultset.
When I delivered my solution my boss sayd don't use where on a stored procedure. But he could not answer the why not.
select * from stored_procedure_here(3) where size > 30;
What are the downsides of this approach. Or are there any? Maybe when the procedure has massive joins in it? It could be used to page some result data without bloating the procedure with lots of extra parameters.
Thanks for your thougths.