Re: Best Practice for Returning Multiple Rows from RPG to PHP

Michael,
I would use the Stored Procedure. You don't need to know the number of
rows to return, you just need a maximum size for your array that will
accomodate the data being returned. How many possible rows are you
returning? If you are returning A LOT of rows maybe you should look at
pagination and design your procedures to handle this by passing From/To
index numbers and returning set sizes of data (10, 100, etc records) at a
time.



Thanks
Bryce Martin
Programmer/Analyst I
570-546-4777



Michael Ryan <michaelrtr@xxxxxxxxx>
Sent by: rpg400-l-bounces@xxxxxxxxxxxx
11/30/2010 09:52 AM
Please respond to
RPG programming on the IBM i / System i <rpg400-l@xxxxxxxxxxxx>


To
"RPG programming on the IBM i / System i" <rpg400-l@xxxxxxxxxxxx>
cc

Subject
Best Practice for Returning Multiple Rows from RPG to PHP






Ok...here's what I really want to know.

What is the best option for returning multiple rows of data from RPG to
PHP?
Here's some of my considerations:

* I don't want to do complex processing in my PHP script; I'd rather use
the
PHP to access and display data;
* The RPG program is needed because I'll be accessing multiple tables and
could be doing some complex processing;
* I need to return 1-n rows of data.
* I'm on V5R4.

When I look at a stored procedure, I see that I can return a result set.
However, I think I need to have an array or a multiple occurrence DS,
which
makes me think I would need to know how many rows I would return. I was
thinking about a UDTF. Would that mean my RPG program would write (INSERT)
records to the UDTF and then my PHP script would just do a simple SELECT?
Does a global temporary table play in this?

I appreciate the insight. Thanks!