From: Andrew Sullivan <ajs@crankycanuck.ca>
To: pgsql-sql@postgresql.org
Subject: Re: Versionning (was: Whole-row comparison)
Date: Fri, 1 Jun 2007 13:47:11 -0400
Message-ID: <20070601174711.GH24299@phlogiston.dyndns.org> (raw)
In-Reply-To: <CCC9DCA122011F4CA593F6A548BFFBD362FCF9@esebe111.NOE.Nokia.com>
References: <CCC9DCA122011F4CA593F6A548BFFBD354D259@esebe111.NOE.Nokia.com>
<473557.7523.qm@web31803.mail.mud.yahoo.com>
<CCC9DCA122011F4CA593F6A548BFFBD354D260@esebe111.NOE.Nokia.com>
<CCC9DCA122011F4CA593F6A548BFFBD362FCF9@esebe111.NOE.Nokia.com>
On Fri, Jun 01, 2007 at 08:07:46PM +0300, christian.roche.ext@nsn.com wrote:
> I've contemplated reusing an awful hack from my Access era, namely using
> a single-rowed table to store the parameter and joining the view on it.
> The parameter would be updated before the view is called; this would
> work but would definitely be ugly. Can someone think of a better way to
> do that ?
I sort of don't see how that hack would be any different from a SRF.
You'd lose the planner benefits anyway, I think, because you'd have
to plan for the generic case where the data could be anything, no?
A
--
Andrew Sullivan | ajs@crankycanuck.ca
Users never remark, "Wow, this software may be buggy and hard
to use, but at least there is a lot of code underneath."
--Damien Katz
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: ajs@crankycanuck.ca
Subject: Re: Versionning (was: Whole-row comparison)
In-Reply-To: <20070601174711.GH24299@phlogiston.dyndns.org>
* 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