| From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Martijn van Oosterhout" <kleptog(at)svana(dot)org>, "Pgsql Hackers" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Creating a Pseudocolumn |
| Date: | 2006-05-15 15:50:49 |
| Message-ID: | 36e682920605150850q30895415i2545fd1c310d6698@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 5/15/06, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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(at)enterprisedb(dot)com
Iselin, New Jersey 08830 | http://www.enterprisedb.com/
"SQL will be the COBOL in the year 2020" -Mike Stonebraker
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Hogan, James F. Jr. | 2006-05-15 15:55:43 | Re: audit table containing Select statements submitted |
| Previous Message | Tom Lane | 2006-05-15 15:43:08 | Re: Creating a Pseudocolumn |