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

From Peter Eisentraut
Subject Re: CURRENT/OLD keywords still broken
Date
Msg-id Pine.LNX.4.30.0012160038080.1319-100000@peter.localdomain
Whole thread Raw
In response to Re: CURRENT/OLD keywords still broken  (Bruce Momjian <pgman@candle.pha.pa.us>)
List 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@gmx.net       http://yi.org/peter-e/



pgsql-hackers by date:

Previous
From: "Oliver Elphick"
Date:
Subject: Re: 7.1 (current) unwanted NOT NULL constraint inserted
Next
From: Bruce Momjian
Date:
Subject: Re: CURRENT/OLD keywords still broken