From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Zeugswetter Andreas <andreas(dot)zeugswetter(at)telecom(dot)at> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: New warning code for missing FROM relations |
Date: | 2000-06-04 17:36:30 |
Message-ID: | 200006041736.NAA20256@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > > If the goal is (a) then your way is better, but I like mine if the goal
> > > is (b). Seems like some discussion is needed here about just what we
> > > want to accomplish.
> >
> > I agree the goal is (b). However, I can not imagine a query with a FROM
> > clause that would ever want to use auto-creation of range entries.
>
> how about:
>
> delete from taba where a=tabb.a;
>
> I think the implicit auto-creation should only be disallowed/warned in
> select statements that have a from clause, not update and delete.
I meant a SELECT FROM clause. A DELETE FROM is not the same, and does
not mark the entry as inFromCl. I should have been more specific.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-06-04 17:48:51 | Re: New warning code for missing FROM relations |
Previous Message | Louis-David Mitterrand | 2000-06-04 15:21:49 | PG 7.0 crash on SELECT |