From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
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 16:02:48 |
Message-ID: | 200908241602.n7OG2mw20105@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Alvaro Herrera wrote:
> 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).
So the problem is that our DELETE ... USING does not allow ANSI join
syntax? Can that be added?
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2009-08-24 16:12:07 | Bug in date arithmetic |
Previous Message | Alvaro Herrera | 2009-08-24 15:54:03 | Re: SIGUSR1 pingpong between master na autovacum launcher causes crash |