Skip site navigation (1) Skip section navigation (2)

Re: [HACKERS] Current sources?

From: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
To: daveh(at)insightdist(dot)com (David Hartwig)
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Current sources?
Date: 1998-05-26 20:24:25
Message-ID: 199805262024.QAA02410@candle.pha.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
> 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

Responses

pgsql-hackers by date

Next:From: Peter T MountDate: 1998-05-26 20:34:19
Subject: Re: [GENERAL] RE: [HACKERS] error messages not only English
Previous:From: Peter T MountDate: 1998-05-26 20:12:09
Subject: Re: [GENERAL] RE: [HACKERS] error messages not only English

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group