> > 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,
Pennsylvania19026
