Re: SQL views over multi member physical file

[CRPence <CRPbottle@xxxxxxxxx>]

  The comment was about using a "TABLE Function", not a "TABLE".  That 
is, a recommendation to defer to a user written program to obtain the 
desired data, requested via an SQL interface [i.e. SELECT] that had been 
defined to the SQL by a prior invocation of the CREATE FUNCTION MyTable 
... RETURNS TABLE.  The data returned by the external program, "an RPG 
program" [which could even be SQLRPG, although the supposed as-implied 
characteristics are not conducive], could effect a dynamic result that 
is automatically refreshed on each invocation; the SQL even has the 
syntax of "NOT DETERMINISTIC" to designate the dynamic nature of a FUNCTION.

Regards, Chuck

On 08 Aug 2013 14:08, Alan Shore wrote:
> but a table wouldn't automatically refresh the f=data and with a
> multitude of users wanting to see this information, it would prove
> to be a !@#$% logistically
>
> Sam_L on  Thursday, August 08, 2013 4:57 PM wrote:
>
> > <<SNIP>> write a User Defined Table function with an RPG program
> > behind it.
> >
> > Select t.*
> > from	mytable('MEMBER_1',500) as t
> >
> > would return the last 500 rows of MEMBER_1.
> >
> > For efficiency, the RPG could <<SNIP>>