I would also suggest that this would complicate grants.  It makes sense that we 
have users who can UPDATE rows, but not remove rows completely, but if this new 
syntax utilizes the DELETE keyword, how would that be implemented from a 
permissions perspective?  We use CI/CD automation for DDL and some DML, and we 
have checks in place that restrict “data removal”.  Utilizing DELETE to UPDATE 
would complicate these guardrails and any others that folks have implemented.

If this is truly functionality you need, maybe wrap the “UPDATE” in a function 
call.

Thanks,
Scott

From: David G. Johnston <david.g.johns...@gmail.com>
Sent: Tuesday, April 22, 2025 9:52 AM
To: Abhishek Hatgine <hatgineabhishe...@gmail.com>
Cc: pgsql-gene...@postgresql.org
Subject: Re: Feature Proposal: Column-Level DELETE Operation in SQL

***This email is from an external source. Only open links and attachments from 
a Trusted Sender.***
On Monday, April 21, 2025, Abhishek Hatgine 
<hatgineabhishe...@gmail.com<mailto:hatgineabhishe...@gmail.com>> wrote:.

  *   More intuitive for developers coming from languages or NoSQL systems 
where fields can be "deleted" from an object/document.
Why should this matter to us?  We don’t have this paradigm, you can’t remove 
columns from existence on a per-row basis.

David J.


Notice of Confidentiality: **This E-mail and any of its attachments may contain 
Lincoln National Corporation proprietary information, which is privileged, 
confidential, or subject to copyright belonging to the Lincoln National 
Corporation family of companies. This E-mail is intended solely for the use of 
the individual or entity to which it is addressed. If you are not the intended 
recipient of this E-mail, you are hereby notified that any dissemination, 
distribution, copying, or action taken in relation to the contents of and 
attachments to this E-mail is strictly prohibited and may be unlawful. If you 
have received this E-mail in error, please notify the sender immediately and 
permanently delete the original and any copy of this E-mail and any printout. 
This email and its attachments may collect your personal information to improve 
Lincoln’s products or to provide you with services related to its products. For 
more information, please see our privacy 
policy.<https://www.lincolnfinancial.com/public/general/privacy> Thank You.**

Reply via email to