🚀 go-pugleaf

OK, I understand.
I wanted to avoid the SELECT because I'm working with EMS SQL MANAGER where I can execute a procedure and its parameters in a graphical user interface for example if the procedure parameters are dates I can select them in a windows-like graphical calendar. So I wanted to show to the end user how to  execute the procedure in that graphical interface and show as a result the table without having to do anything else, but it's not very important, I'll do the SELECT. 


"Wayne Niddery [TeamB]" <wniddery@chaffaci.on.ca> wrote:
>aleplgr wrote:
>> Hi! In a stored procedure I process a table and to show it to the end
>> user now I  have to execute a SELECT at the client side,out of the
>> SP, this SELECT shows the end user a 4 columns,500 rows table. Is it
>> possible to execute the SELECT in the SP? so that the end user only
>> runs the SP and it returns the result table without having to run the
>> SELECT after the execution of the stored procedure.
>
>Being able to select from a stored procedure is exactly the way to do this - 
>Select is the SQL means of returning a result set. Simply executing a stored 
>procedure can only return a single row of values.
>
>Can you explain why you think you need to avoid calling select on the client 
>side?
>
>-- 
>Wayne Niddery - Winwright, Inc (www.winwright.ca)
>"The two most abundant elements in the universe are hydrogen and
>stupidity." - Harlan Ellison 
>
>