> The second option (your earlier suggestion) seems to be necessary and sufficient. The junk filter (and
> jf_cleanTupType) will always exist, for SELECT statements, as long as the following is not a legal statement:
> SELECT FROM foo GROUP BY bar;
> Currently the parser will not accept it. Sufficient.
> The first option will set tupType, for non-SELECT statements, to something it otherwise may not have been.
> I would rather not risk effecting those calling routines which are not executing a SELECT command. At this
> time, I do not understand them enough, and I see no benefit. Necessary?
OK, I will leave it alone. Is there a way to use junk filters only in
cases where we need them?
Bruce Momjian | 830 Blythe Avenue
maillist(at)candle(dot)pha(dot)pa(dot)us | Drexel Hill, Pennsylvania 19026
+ If your life is a hard drive, | (610) 353-9879(w)
+ Christ can be your backup. | (610) 853-3000(h)
In response to
pgsql-hackers by date
|Next:||From: Peter T Mount||Date: 1998-05-26 20:34:19|
|Subject: Re: [GENERAL] RE: [HACKERS] error messages not only English |
|Previous:||From: Peter T Mount||Date: 1998-05-26 20:12:09|
|Subject: Re: [GENERAL] RE: [HACKERS] error messages not only English|