Re: [HACKERS] Re: [PORTS] Port Bug Report: int2 negative numbers not parsed correctly
| От | Thomas G. Lockhart |
|---|---|
| Тема | Re: [HACKERS] Re: [PORTS] Port Bug Report: int2 negative numbers not parsed correctly |
| Дата | |
| Msg-id | 352269F9.9C57968B@alumni.caltech.edu обсуждение исходный текст |
| Ответ на | Re: [PORTS] Port Bug Report: int2 negative numbers not parsed correctly (Bruce Momjian <maillist@candle.pha.pa.us>) |
| Ответы |
Re: [HACKERS] Re: [PORTS] Port Bug Report: int2 negative numbers not parsed correctly
|
| Список | pgsql-hackers |
> > Well we maybe can, but it sure is ugly. This will be spread around a
> > bunch of places (everywhere there is a unary minus allowed). I
> > already did the wrong thing and brute-forced something similar into
> > the CREATE SEQUENCE code in gram.y. Isolating it in transform_expr()
> > or somewhere like that would be much cleaner.
> But isn't it is just one line in gram.y. That is where I was seeing
> it happen.
golem$ grep UMINUS gram.y
%right UMINUS
| '-' default_expr %prec UMINUS
| '-' constraint_expr %prec UMINUS
| '-' a_expr %prec UMINUS
| '-' b_expr %prec UMINUS
| '-' position_expr %prec UMINUS
So at least 5 different places, perhaps more when you get into it :(
- Tom
В списке pgsql-hackers по дате отправления: