| From: | Surafel Temesgen <surafel3000(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | DELETE and UPDATE with LIMIT and ORDER BY |
| Date: | 2017-04-24 15:09:18 |
| Message-ID: | CALAY4q9fcrscybax7fg_uojFwjw_Wg0UMuSrf-FvN68SeSAPAA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
the necessity of allowing limit and order by clause to be used with delete
and
update statement is discussed in the past and added to the todo list
preveouse mailing list descissions
http://archives.postgresql.org/pgadmin-hackers/2010-04/msg00078.php
http://archives.postgresql.org/pgsql-hackers/2010-11/msg01997.php
i attached a small patch for its implementation.
Notice : inorder to avoid unpredictable result the patch did not allow
limit clause without order by and vise versal.
comment please?
Regareds
Surafel
| Attachment | Content-Type | Size |
|---|---|---|
| delete_update_with_limit_orderby_v1.patch | application/octet-stream | 20.2 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Craig Ringer | 2017-04-24 15:14:40 | Re: OK, so culicidae is *still* broken |
| Previous Message | Nikhil Sontakke | 2017-04-24 15:01:32 | Re: StandbyRecoverPreparedTransactions recovers subtrans links incorrectly |