| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Adriaan Joubert <a(dot)joubert(at)albourne(dot)com>, pgsql-hackers(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: [HACKERS] Re: Join/table alias bug |
| Date: | 2000-04-21 22:06:46 |
| Message-ID: | Pine.LNX.4.21.0004211905320.351-100000@localhost.localdomain |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
Tom Lane writes:
> Not only for historical reasons: there are cases where it allows you
> to do things you couldn't easily do otherwise. An example is deleting
> using a join:
>
> DELETE FROM target WHERE field1 = source.field2
Wow, that seems pretty bogus to me.
> Bruce had actually put in some code to emit warnings, but Thomas
> objected to it for reasons I don't recall clearly.
I think it was along the lines of "it's not the backend's task to teach
SQL". Incidentally, it could be, with the SQL flagger (sec. 4.34).
--
Peter Eisentraut Sernanders väg 10:115
peter_e(at)gmx(dot)net 75262 Uppsala
http://yi.org/peter-e/ Sweden
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Frank Mayhar | 2000-04-24 15:43:19 | Crash in PostgreSQL 7.0.b5. |
| Previous Message | Bruce Momjian | 2000-04-20 15:44:50 | Re: libpq++ update |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim Mercer | 2000-04-26 17:22:11 | pgsql/php3/apache authentication |
| Previous Message | Tom Lane | 2000-04-20 14:40:53 | Re: [HACKERS] Re: Join/table alias bug |