Re: Creating unique or "internal-use-only" column names (ColumnRef) - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Creating unique or "internal-use-only" column names (ColumnRef)
Date
Msg-id 20150907132806.GN2912@alvherre.pgsql
Whole thread Raw
In response to Creating unique or "internal-use-only" column names (ColumnRef)  (Peter Moser <pitiz29a@gmail.com>)
Responses Re: Creating unique or "internal-use-only" column names (ColumnRef)  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
Peter Moser wrote:
> Good afternoon,
> is it possible to create unique column names or to give column names inside
> the parser phase that do not interfer with the outside world, i.e. with
> column names from tables or aliases given by the user.
> 
> Some short background:
> I created my own from-clause-item, that gets rewritten into a sub-query. I
> do this because I want to re-use existing code as much as possible. The
> rewritten sub-query gets transformed with "transformRangeSubselect"...
> Within this sub-query I need 3 columns that shouldn't interfer with columns
> from the input. We refer to them from a JOIN-ON clause and an ORDER-BY
> clause.

This seems pretty much the same as a junk attribute, if I understand you
correctly.  I suggest given a look at how those work.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Thomas Munro
Date:
Subject: Re: synchronous_commit = apply
Next
From: Alexander Korotkov
Date:
Subject: Re: WIP: Access method extendability