Re: CURRENT/OLD keywords still broken - Mailing list pgsql-hackers

From Tom Lane
Subject Re: CURRENT/OLD keywords still broken
Date
Msg-id 14073.976921518@sss.pgh.pa.us
Whole thread Raw
In response to CURRENT/OLD keywords still broken  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> peter=# select 1 as current;
>  old
> -----
>    1

> This is now the inverse of what it used to do, but it's still not what it
> *should* do.  I see someone already tried to fix that (keywords.c 1.76 ->
> 1.77, TODO list), but he should try again.

We should rip out the whole current/old aliasing, IMHO.  CURRENT has
been unsupported for a version or two now, hasn't it?

I had that on my personal TODO list, but I was going to leave it till
after 7.1 because I had mistakenly thought that CURRENT was still a
keyword in 7.0.  But it wasn't, was it?  Bruce, why did you put in
that mapping?
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Views as FROM subselects
Next
From: Tom Lane
Date:
Subject: Re: TOAST-table vacuuming (was Re: Idea for reducing pl anning time)