From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Philip Warner <pjw(at)rhyme(dot)com(dot)au>, Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>, "'PostgreSQL-development'" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: AW: New warning code for missing FROM relations |
Date: | 2000-06-05 17:06:10 |
Message-ID: | 200006051706.NAA05846@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Philip Warner <pjw(at)rhyme(dot)com(dot)au> writes:
> > I take it that there is no chance of a compile-time or runtime option to
> > disallow this kind of thing in all cases?
>
> Define "all cases" ... also, just how strict do you want to be?
> Disallow use of *any* Postgres feature that is not in SQL92 (that
> would include all user datatypes and functions, for example)?
>
> Postgres was never designed as an SQL compatibility checker, and
> I doubt that it'd be cost-effective to try to turn it into one.
> A standalone tool might be a better approach.
>
> Perhaps there is someone out there who wants this feature badly
> enough to do the legwork, but I'm not him ;-)
Agreed. Seems the current warning level as configured is in the middle
of people's expections on this issue.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-06-05 17:07:30 | Re: 7.0.1 Problems. |
Previous Message | Bruce Momjian | 2000-06-05 17:05:02 | Re: [HACKERS] INSTALL/install.sgml file |