Re: Creating a Pseudocolumn - Mailing list pgsql-hackers

From Jonah H. Harris
Subject Re: Creating a Pseudocolumn
Date
Msg-id 36e682920605150850q30895415i2545fd1c310d6698@mail.gmail.com
Whole thread Raw
In response to Re: Creating a Pseudocolumn  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 5/15/06, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> This could only work if LEVEL is guaranteed to have one and only one
> value per tuple.  I'm not too sure about the spec but it seems like
> that'd probably fall down in join situations.

Yes, this was another thing handled by Evgen's patch... FakeVar could
only exist once and was ignored in joins.  So, basically (like
rownum), I have to create a pseudocolumn that isn't bound by joins.

Do you know of any way around this?

--
Jonah H. Harris, Software Architect | phone: 732.331.1300
EnterpriseDB Corporation            | fax: 732.331.1301
33 Wood Ave S, 2nd Floor            | jharris@enterprisedb.com
Iselin, New Jersey 08830            | http://www.enterprisedb.com/

"SQL will be the COBOL in the year 2020" -Mike Stonebraker


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Creating a Pseudocolumn
Next
From: "Hogan, James F. Jr."
Date:
Subject: Re: audit table containing Select statements submitted