From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Jean-Michel Pouré <jm(at)poure(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: DELETE syntax on JOINS |
Date: | 2009-08-24 15:42:14 |
Message-ID: | 20090824154213.GB5962@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Bruce Momjian wrote:
> > Ultimately, why not allow:
> >
> > DELETE h, tn
> > FROM history AS h
> > INNER JOIN term_node AS tn ON (h.nid = tn.nid)
> > INNER JOIN term_data AS td ON (td.tid = tn.tid)
> > WHERE h.uid = 2067 AND td.vid = 2
> >
> > IMHO this would improve compliance towards other database systems. To me
> > this seems to be in the reasonable scope of compatibility.
>
> Which "other database systems"? Only MySQL? If it is MySQL-only, we
> are unlikely to add it.
The SQL standard does not support this syntax. They would have you put
the joins in a subselect (which is often not enough because then you
can't use outer joins).
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-08-24 15:51:54 | Re: SIGUSR1 pingpong between master na autovacum launcher causes crash |
Previous Message | Tom Lane | 2009-08-24 15:29:25 | Re: hba load error and silent mode |