From: | "Jonah H(dot) Harris" <jonah(dot)harris(at)gmail(dot)com> |
---|---|
To: | "Pgsql Hackers" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Creating a Pseudocolumn |
Date: | 2006-05-15 15:03:46 |
Message-ID: | 36e682920605150803l4e32ba18i68def954d0f56c27@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hey everyone,
I'm reworking hierarchical queries and am adding a LEVEL pseudocolumn.
As it's a totally calculated attribute, what's the best way to handle
it keeping in mind that LEVEL is only used in a hierarchical query?
Looking at Evgen's patches, if he recognizes a hierarchical query and
finds a LEVEL column in the target list, he creates a FakeVar (similar
to Var) entry for it which is then passed throughout the system and
modified on a per-tuple basis. While this works, it seems a bit
kludgy and requires a good amount of special-case code. As such, I
was wondering if you guys have some suggestions on how to use what's
already there to accomplish the same thing.
I couldn't think of any pseudocolumns like this in PostgreSQL, but I
may just be brain-dead again. As it may be sorta similar, how were we
discussing handling rownum?
--
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/
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2006-05-15 15:08:22 | Re: Creating a Pseudocolumn |
Previous Message | Hogan, James F. Jr. | 2006-05-15 14:38:54 | Re: audit table containing Select statements submitted |