public inbox for [email protected]
help / color / mirror / Atom feedFrom: Deas, Scott <[email protected]>
To: David G. Johnston <[email protected]>
To: Abhishek Hatgine <[email protected]>
Cc: [email protected] <[email protected]>
Subject: RE: Feature Proposal: Column-Level DELETE Operation in SQL
Date: Tue, 22 Apr 2025 17:54:43 +0000
Message-ID: <SA1PR22MB4209DFCCD303F4886794B2799ABB2@SA1PR22MB4209.namprd22.prod.outlook.com> (raw)
In-Reply-To: <CAKFQuwbyC8AB3P2rGEM1+V6YLTH6jfMG0Vp52+oj1hbjnUZT7g@mail.gmail.com>
References: <CAD2voTQMUmNCKBok-_HvYLqFNECRWNkvqPruq0NcsFgd6g-Odw@mail.gmail.com>
<CAKFQuwbyC8AB3P2rGEM1+V6YLTH6jfMG0Vp52+oj1hbjnUZT7g@mail.gmail.com>
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 <[email protected]>
Sent: Tuesday, April 22, 2025 9:52 AM
To: Abhishek Hatgine <[email protected]>
Cc: [email protected]
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 <[email protected]<mailto:[email protected]>> 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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: RE: Feature Proposal: Column-Level DELETE Operation in SQL
In-Reply-To: <SA1PR22MB4209DFCCD303F4886794B2799ABB2@SA1PR22MB4209.namprd22.prod.outlook.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox