mlw wrote:
> Jan Wieck wrote:
> >
> > mlw wrote:
> > > [...]
> > >
> > > IMHO modifying the function manager to allow the return of a full row, and a
> > > "set of" full rows, answers a LOT of issues I have seen over the years with
> > > PostgreSQL extensibility.
> >
> > Sure. Actually I thin
Jeff Davis <[EMAIL PROTECTED]>,
PostgreSQL-development <[EMAIL PROTECTED]>
Subject: Re: [HACKERS] Again, sorry, caching, (Tom What do you think: function
On 19 Mar 2002, Greg Copeland wrote:
> On Tue, 2002-03-19 at 07:46, mlw wrote:
> [snip]
>
> > Right now, the function
Jan Wieck wrote:
>
> mlw wrote:
> > [...]
> >
> > IMHO modifying the function manager to allow the return of a full row, and a
> > "set of" full rows, answers a LOT of issues I have seen over the years with
> > PostgreSQL extensibility.
>
> Sure. Actually I think you'll have an easy project
Gavin Sherry wrote:
> I'm not sure that cached results is a direction postgres need move in. But
> if it does, I think this a better way to do it (given that I may have
> overlooked something) than modifying the function manager (argh!).
I actually had an anterior motive.
Your comment about cach
On 19 Mar 2002, Greg Copeland wrote:
> On Tue, 2002-03-19 at 07:46, mlw wrote:
> [snip]
>
> > Right now, the function manager can only return one value, or one set of values
> > for a column. It should be possible, but require a lot of research, to enable
> > the function manager to return a set
On Tue, 2002-03-19 at 07:46, mlw wrote:
> I was thinking about this. There seems to be a consensus that caching means no
> ACID compliance. And everyone seems to think it needs to be limited. We can
> implement a non-ACID cache as a contrib function with some work to the function
> manager.
Until
On Tue, 2002-03-19 at 07:46, mlw wrote:
[snip]
> Right now, the function manager can only return one value, or one set of values
> for a column. It should be possible, but require a lot of research, to enable
> the function manager to return a set of rows. If we could get that working, it
> could
