> At one time Bruce had made some patches to emit informative notice
> messages about implicit FROM entries, but that got turned off again
> for reasons that I forget...
It was triggered with common cases from the "outer join" syntax. It took
a while to track down since it was introduced while I was working on the
syntax feature :(
If it *really* needs to be put back in, then we should do so with a flag
so we can disable the warning at compile time, run time, and/or in the
outer join parser area. But imho sprinkling the parser with warnings for
allowed syntax is heading the wrong direction. If it is legal, allow it.
If it is illegal, disallow it. If it is confusing for some, but works
fine for others, it shouldn't become "sort of legal" with a warning.
In response to
pgsql-hackers by date
|Next:||From: D'Arcy J.M. Cain||Date: 2000-05-31 02:23:27|
|Subject: Announce: Release of PyGreSQL version 3.0|
|Previous:||From: Mitch Vincent||Date: 2000-05-31 01:53:01|
|Subject: Re: Full text indexing preformance! (long) |
pgsql-sql by date
|Next:||From: SL Baur||Date: 2000-05-31 04:31:23|
|Subject: Re: Pg/PLSQL Errors!!|
|Previous:||From: Mitch Vincent||Date: 2000-05-31 01:49:51|
|Subject: Re: does the' text' type cann't store more than 20,000char ?|