Re: CURRENT/OLD keywords still broken

From: Bruce Momjian <pgman(at)candle(dot)pha(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 22:58:06
Message-ID: 200012152258.RAA08165@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 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.

That was me. The old code did old -> current, so I changed it to do
current -> old. How else can I fix this? Attached is the old patch.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

Attachment Content-Type Size
unknown_filename text/plain 1.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-12-15 22:59:52 Views as FROM subselects
Previous Message Peter Eisentraut 2000-12-15 22:53:53 CURRENT/OLD keywords still broken