From: | "Shridhar Daithankar" <shridhar_daithankar(at)persistent(dot)co(dot)in> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: FETCH a cursor inside a SELECT |
Date: | 2002-11-29 13:42:34 |
Message-ID: | 3DE7BC22.20902.6651785@localhost |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 29 Nov 2002 at 23:33, David Crawshaw wrote:
> I've been working with this all day, and I'm finally out of ideas.
> Hopefully someone has encountered a situation like this before.
>
> Originally I was going to write a function that returned a series of
> id's, but this caused no end of confusion on PG 7.2.3. Instead, I've
> decided to return cursors.
>
> matchClass1 works as expected. However in matchClass2, I wish to exclude
> all of the results from matchClass1. This inline fetch gives me the
> following error calling matchClass2:
How about defining two views? One view that returns matchclass1 and another
selects on this view to eliminate duplicates.
i.e. using views as functions/cursors returning multiple recordset..
Just a thought.. Did not follow earlier thread so might be next to useless as
well..
Bye
Shridhar
--
"We'll look into it": By the time the wheels make a full turn, we assume you
will have forgotten about it, too.
From | Date | Subject | |
---|---|---|---|
Next Message | David Crawshaw | 2002-11-29 13:51:21 | Re: FETCH a cursor inside a SELECT |
Previous Message | Jim Worke | 2002-11-29 13:38:43 | Re: Bad timestamp external representation |