| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: CURRENT/OLD keywords still broken |
| Date: | 2000-12-15 23:39:22 |
| Message-ID: | Pine.LNX.4.30.0012160038080.1319-100000@peter.localdomain |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian 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.
>
> 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.
Maybe add another branch into the SpecialRuleRelation grammar rule with
CURRENT instead of OLD.
--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2000-12-16 00:07:00 | anoncvs's lock |
| Previous Message | Bruce Momjian | 2000-12-15 23:36:32 | Re: CURRENT/OLD keywords still broken |