| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
| Cc: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, "'Peter Eisentraut'" <peter_e(at)gmx(dot)net>, "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "'PostgreSQL-development'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: AW: New warning code for missing FROM relations |
| Date: | 2000-06-05 15:44:46 |
| Message-ID: | 12197.960219886@sss.pgh.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 ;-)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-06-05 16:03:20 | Re: Problems with char array set to NULL |
| Previous Message | Tom Lane | 2000-06-05 15:37:43 | Re: [HACKERS] INSTALL/install.sgml file |