I have an application that has a search panel where users can enter
things like date ranges, invoice numbers, etc. I'm wondering if it
would be 'good design' to make a stored procedure that took search
criteria from the user and pieced together the query to run within the
procedure, vs. granting read-only access to the table and having the
application itself piece the sql together.
I generally don't like embedding sql in applications because database
schemas tend to change, and trying to track down applications with
outdated sql is not fun. But how else do you allow reporting /
searching on your database?. Only other way would be to create a view
and have apps search on that, but then you're still stuck sending
lengthy sql statements across the network.
Received on Mon Jan 21 2002 - 13:33:07 CST
