| From: | Andrew Sullivan <ajs(at)crankycanuck(dot)ca> |
|---|---|
| To: | pgsql-sql(at)postgresql(dot)org |
| Subject: | Re: Versionning (was: Whole-row comparison) |
| Date: | 2007-06-01 17:47:11 |
| Message-ID: | 20070601174711.GH24299@phlogiston.dyndns.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-sql |
On Fri, Jun 01, 2007 at 08:07:46PM +0300, christian(dot)roche(dot)ext(at)nsn(dot)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(at)crankycanuck(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | christian.roche.ext | 2007-06-01 18:07:10 | Re: Versionning (was: Whole-row comparison) |
| Previous Message | christian.roche.ext | 2007-06-01 17:07:46 | Versionning (was: Whole-row comparison) |