From: Markus Schaber <schabi@logix-tt.com>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: PostGIS Users Discussion <postgis-users@postgis.refractions.net>
Cc: PostgreSQL SQL List <pgsql-sql@postgresql.org>
Subject: Re: Problem using set-returning functions
Date: Mon, 27 Mar 2006 17:14:50 +0200
Message-ID: <4428016A.7020006@logix-tt.com> (raw)
In-Reply-To: <20060327070103.U96317@megazone.bigpanda.com>
References: <20060324200036.ED8E52C1503@netnation.refractions.net>
<1143278826.44250cea7eccc@web-mail1.uibk.ac.at>
<4427BFE4.8050500@logix-tt.com>
<4427C15C.5070905@logix-tt.com>
<7DB6EE64-AB49-4DA6-B690-21A53FD6045E@pgedit.com>
<4427F003.2070705@logix-tt.com>
<20060327070103.U96317@megazone.bigpanda.com>
Hi, Stephan,
Stephan Szabo wrote:
> It's an implementation detail. Some languages handle SRFs in a way that
> can be handled in the select list (SQL and C I think) and others do not
> (plpgsql).
Ah, that's an enlightening explanation, thanks.
> The latter will likely change at some point, although there are
> some confusing issues with SRFs in the select list as well, see the
> difference in behavior between:
>
> select generate_series(1,10), generate_series(1,5);
> vs
> select * from generate_series(1,10) g1, generate_series(1,5) g2;
I know that the SRF special semantics are ugly, and would vote for
adjacent tables to be implemented as replacement.
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: schabi@logix-tt.com, sszabo@megazone.bigpanda.com, postgis-users@postgis.refractions.net
Subject: Re: Problem using set-returning functions
In-Reply-To: <4428016A.7020006@logix-tt.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox