From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: CURRENT/OLD keywords still broken |
Date: | 2000-12-15 23:05:18 |
Message-ID: | 14073.976921518@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Peter Eisentraut <peter_e(at)gmx(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-12-15 23:08:08 | Re: TOAST-table vacuuming (was Re: Idea for reducing pl anning time) |
Previous Message | Bruce Momjian | 2000-12-15 22:59:52 | Views as FROM subselects |