
> > >	SELECT *
> > >	   INTO TABLE tmp1
> > >	   FROM tmp
> > >	   WHERE onek.unique1 < 2;
> > >	NOTICE:  Adding missing FROM-clause entry for table onek
> 
> > Is is worth adding yet another setting, eg. set sql92=strict, which
> > would disallow such flagrant breaches of the standard?
> 
> SQL provides for facility called the SQL Flagger, which is 
> supposed to do
> exactly that. This might sound like an interesting idea but 
> in order for
> it to be useful you'd have to maintain it across the board, 
> which sounds
> like a major head ache.
> 
> The irony in the given example is that the SELECT INTO 
> command isn't in
> the standard in the first place so you'd have to create all sorts of
> double standards. Certain things would be "extensions", certain things
> would be "misuse". And for all it's worth, we have no idea 
> which is which.
> 
> If you want to throw about warnings about "probable" coding 
> errors and the
> like one *must* be able to switch them off. Either something is right,
> then you shut up. Or it's wrong, then you throw an error. Or 
> you're not
> sure, then you better leave it up to the user.

Yes, only Bruce and I are of the opinion that it *is* an Error, and I guess 
we want some consensus.
The notice is imho of the sort: notice this syntax is going to be disallowed
soon.

Andreas

Mon, 5 Jun 2000 10:02:55 +0200 
Zeugswetter Andreas SB <ZeugswetterA@wien.spardat.at>
AW: New warning code for missing FROM relations
> > The irony in the given example is that the SELECT INTO 
> > command isn't in
> > the standard in the first place so you'd have to create all sorts of
> > double standards. Certain things would be "extensions", certain things
> > would be "misuse". And for all it's worth, we have no idea 
> > which is which.
> > 
> > If you want to throw about warnings about "probable" coding 
> > errors and the
> > like one *must* be able to switch them off. Either something is right,
> > then you shut up. Or it's wrong, then you throw an error. Or 
> > you're not
> > sure, then you better leave it up to the user.
> 
> Yes, only Bruce and I are of the opinion that it *is* an Error, and I guess 
> we want some consensus.
> The notice is imho of the sort: notice this syntax is going to be disallowed
> soon.

I see the notice as "Hey, you probably did something you didn't want to do".

-- 
  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, Pennsylvania 19026

Mon, 5 Jun 2000 06:25:12 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: AW: New warning code for missing FROM relations
Bruce Momjian writes:

> I see the notice as "Hey, you probably did something you didn't want
> to do".

Again, "probably" means you're not sure, so you leave it up to the user to
turn it on or off.

-- 
Peter Eisentraut                  Sernanders vï¿½g 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden


Tue, 6 Jun 2000 18:08:04 +0200 (CEST)
Peter Eisentraut <peter_e@gmx.net>
Re: AW: New warning code for missing FROM relations
Zeugswetter Andreas SB writes:

> Yes, only Bruce and I are of the opinion that it *is* an Error, and I
> guess we want some consensus.

I agree that it is an error.

> The notice is imho of the sort: notice this syntax is going to be
> disallowed soon.

If you can guarantee that each user will only see the notice once, then
okay. :)

-- 
Peter Eisentraut                  Sernanders vï¿½g 10:115
peter_e@gmx.net                   75262 Uppsala
http://yi.org/peter-e/            Sweden



Tue, 6 Jun 2000 18:09:00 +0200 (CEST)
Peter Eisentraut <peter_e@gmx.net>
Re: AW: New warning code for missing FROM relations
[ Charset ISO-8859-1 unsupported, converting... ]
> Zeugswetter Andreas SB writes:
> 
> > Yes, only Bruce and I are of the opinion that it *is* an Error, and I
> > guess we want some consensus.
> 
> I agree that it is an error.
> 
> > The notice is imho of the sort: notice this syntax is going to be
> > disallowed soon.
> 
> If you can guarantee that each user will only see the notice once, then
> okay. :)

There is no sense that this is a warning about the syntax changing at
some point.  It is to warn queries that are probably broken.

Seems if they already have a FROM clause, there is no purpose for some
tables being in the FROM clause, and others begin auto-created.  In
other cases, it issues no warning.

-- 
  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, Pennsylvania 19026

Tue, 6 Jun 2000 12:13:31 -0400 (EDT)
Bruce Momjian <pgman@candle.pha.pa.us>
Re: AW: New warning code for missing FROM relations