Chris Mungall <[EMAIL PROTECTED]> writes:
> On Mon, 1 Aug 2005, Tom Lane wrote:
>> Chris Mungall <[EMAIL PROTECTED]> writes:
>>> What are the reasons for deprecating the use of the function in the
>>> SELECT clause?
>>
>> The semantics of having more than one set-returning function in the
>> targe
On Mon, 1 Aug 2005, Tom Lane wrote:
> Chris Mungall <[EMAIL PROTECTED]> writes:
> > What are the reasons for deprecating the use of the function in the
> > SELECT clause?
>
> The semantics of having more than one set-returning function in the
> target list are, um, poorly thought out. However, w
Chris Mungall <[EMAIL PROTECTED]> writes:
> What are the reasons for deprecating the use of the function in the
> SELECT clause?
The semantics of having more than one set-returning function in the
target list are, um, poorly thought out. However, we haven't removed
the feature because (as you not
Hi all,
I have a question on functions returning sets. I have a lot of complex
functionality I would like to keep in the DBMS rather than in an
application, and I would like this functionality to be available as
queries over standard SQL relations.
Section 31.4.4 of the docs
(http://www.postgres
Title: Re: [SQL] How to connect ORACLE database from Postgres function using
plpgsql/pltclu?
Thanks Sean, It great help from you.
Thanks
Dinesh Pandey
From: Sean Davis [mailto:[EMAIL PROTECTED]
Sent: Monday, August 01, 2005 4:47
PM
To: [EMAIL PROTECTED]
Cc: PostgreSQL
Subject:
Title: Re: [SQL] How to connect ORACLE database from Postgres function using plpgsql/pltclu?
On 8/1/05 6:35 AM, "Dawid Kuroczko" <[EMAIL PROTECTED]> wrote:
On 8/1/05, Dinesh Pandey <[EMAIL PROTECTED]> wrote:
> Is there any way to connect ORACLE database from Postgres function using
> plpgsql/
On 8/1/05, Dinesh Pandey <[EMAIL PROTECTED]> wrote:
> Is there any way to connect ORACLE database from Postgres function using
> plpgsql/pltclu?
With PLpgSQL I don't think its possible. I don't know how about PLtclU (should
be possible), but I'm sure its doable from PLperlU (using DBI). Don't e
Am Samstag, 30. Juli 2005 17:15 schrieb Tom Lane:
> The unconstrained join against pg_user is clearly unnecessary,
> and in fact I took it out a few days ago. I'm not sure whether the
> SELECT DISTINCT is still needed --- it might be, if there can be
> multiple pg_depend entries linking the same e
