Re: AW: New warning code for missing FROM relations
| От | Philip Warner |
|---|---|
| Тема | Re: AW: New warning code for missing FROM relations |
| Дата | |
| Msg-id | 3.0.5.32.20000606144135.022e3b90@mail.rhyme.com.au обсуждение исходный текст |
| Ответ на | Re: AW: New warning code for missing FROM relations (Tom Lane <tgl@sss.pgh.pa.us>) |
| Список | pgsql-hackers |
At 11:44 5/06/00 -0400, Tom Lane wrote: >Philip Warner <pjw@rhyme.com.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)? Sorry, I should have been a bit more specific! I would like some kind of option to disable all cases of adding tables to FROM clauses by implication. The main issue I have with this feature is it is more likely to be used (by me) by accident (as a result of a typo), and consequently introduce very strange results. I am unaware (yet? ;-}) of any other non-SQL features in PostgreSQL that are likely to cause me the same level of concern. Adding tables to a query seems very dangerous: some people might, for example, expect an automatic natural join on primary/foreign keys if you add a table. ---------------------------------------------------------------- Philip Warner | __---_____ Albatross Consulting Pty. Ltd. |----/ - \ (A.C.N. 008 659 498) | /(@) ______---_ Tel: +61-500 83 82 81 | _________ \ Fax: +61-500 83 82 82 | ___________ | Http://www.rhyme.com.au | / \| | --________-- PGP key available upon request, | / and from pgp5.ai.mit.edu:11371 |/
В списке pgsql-hackers по дате отправления: