Re: New warning code for missing FROM relations
От | Bruce Momjian |
---|---|
Тема | Re: New warning code for missing FROM relations |
Дата | |
Msg-id | 200006040258.WAA29574@candle.pha.pa.us обсуждение исходный текст |
Ответ на | Re: New warning code for missing FROM relations (Philip Warner <pjw@rhyme.com.au>) |
Ответы |
Re: New warning code for missing FROM relations
|
Список | pgsql-hackers |
> At 00:40 3/06/00 -0400, Bruce Momjian wrote: > > > >The regression tests run fine, except for: > > > > SELECT * > > INTO TABLE tmp1 > > FROM tmp > > WHERE onek.unique1 < 2; > > NOTICE: Adding missing FROM-clause entry for table onek > > Personally I would prefer this to generate an error, eg: > > Table 'onek' refereenced in the WHERE clause is not in the FROM clause. Yes, that was one of my stated options, return an error. > Is is worth adding yet another setting, eg. set sql92=strict, which would > disallow such flagrant breaches of the standard? Maybe it could even be set > as the default in template1? I understand that breaking legacy code is a > bad idea, so the warning is a good step, but I would prefer an error if I > ever write such a statement. I am concerned about overloading the SET command. Seems we should just agree on a behavior. -- Bruce Momjian | http://www.op.net/~candle pgman@candle.pha.pa.us | (610) 853-3000+ If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup. | Drexel Hill, Pennsylvania19026
В списке pgsql-hackers по дате отправления: