Thank you, Robert and Tom, for sharing your valuable insights, and apologies for the slight delay in my response. From the discussion, what I understand is that we aim to extend the current DROP ROLE syntax to include the CASCADE/RESTRICT option, which has been introduced in the latest SQL standard, as mentioned by Tom. However, as Robert pointed out, implementing the CASCADE option for handling dependent objects that span multiple databases is not feasible at the moment. The RESTRICT option, as I understand it, is already the default behavior. Therefore, we will proceed with implementing the CASCADE/RESTRICT syntax specifically for handling dependent roles, rather than the dependent database objects like tables, views, etc., which can span multiple databases.
Please correct me if I’m mistaken or if there’s anything I’ve missed in my understanding. thanks. -- With Regards, Ashutosh Sharma.
