| From: | Hunaid Sohail <hunaidpgml(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers(at)postgresql(dot)org |
| Cc: | Peter Eisentraut <peter(at)eisentraut(dot)org>, Christoph Berg <myon(at)debian(dot)org>, Robert Treat <rob(at)xzilla(dot)net>, Kacper Kuras <kacperkuras(at)hotmail(dot)com> |
| Subject: | Re: Proposal: SELECT * EXCLUDE (...) command |
| Date: | 2026-10-28 14:12:54 |
| Message-ID: | CAMWA6yZieJpgzzZ-rvix2pq-hRs+X4RSeB-hT3cLwxCjO97+AQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hello,
PFA v4 of the patch with following changes:
Staroptions scope is limited now by throwing errors from C
functions (instead of gram.y) if used with expressions or other
clauses like where/order by etc as reported above by Kacper.
Since there were no other opinions (or objections) so
RETURNING is now allowed with staroptions.
Apart from code refactoring, a few more regression tests are
added regarding RETURNING clause and nested queries.
It would be nice to get some kind of update regarding this
feature in SQL Standard to see if we are going in the
right direction.
Regards,
Hunaid Sohail
| Attachment | Content-Type | Size |
|---|---|---|
| v4-0001-Implement-SELECT-EXCLUDE-REPLACE-RENAME-clauses.patch | application/x-patch | 91.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Previous Message | John Naylor | 2026-10-28 14:11:45 | Re: Quickselect instead of a heap for ORDER BY ... LIMIT N large bounded sorts |