From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Jean-Michel Pouré <jm(at)poure(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: DELETE syntax on JOINS |
Date: | 2009-08-22 15:17:00 |
Message-ID: | 200908221517.n7MFH0K17833@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jean-Michel Pour wrote:
-- Start of PGP signed section.
> Dear Friends,
>
> First, thank you very much for considering a fix on the GROUP BY issue.
> I am starting a new thread about another issue:
>
> It seems that DELETE cannot understand INNER JOINS and needs HAVING.
>
> Read:
> http://drupal.org/node/555562 (main message)
> http://drupal.org/node/555648
>
> I don't see why PostgreSQL would not be able to run queries like:
>
> DELETE h
> 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
>
> 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.
--
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 | Tom Lane | 2009-08-22 15:59:07 | Resjunk sort columns, Heikki's index-only quals patch, and bug #5000 |
Previous Message | Tom Lane | 2009-08-22 15:14:27 | Re: Index-only quals |