Regarding feature #6367 "DROP DATABASE can now take the option FORCE ..." - Mailing list pgadmin-hackers

From Akshay Joshi
Subject Regarding feature #6367 "DROP DATABASE can now take the option FORCE ..."
Date
Msg-id CANxoLDe8jKs8GQN-69jM5SJV6URcJUsr80sG64BbDjUqeeibFQ@mail.gmail.com
Whole thread Raw
Responses Re: Regarding feature #6367 "DROP DATABASE can now take the option FORCE ..."
List pgadmin-hackers
Hi Hackers

I have started the implementation for feature #6367 "DROP DATABASE can now take the option FORCE to drop a database even if other users are connected".

For that, I figure out two places one in the Properties tab of the Databases collection node and the other in the context menu on the individual database node except the maintenance database. This feature will be available from PG 13 and above. Please refer to the screenshot below:

Properties.png   The 'Drop with Force' button is visible only on the Databases collection node. For other collection nodes, it is a 'Drop Cascade'.


Context Menu.png 

Please review and let me know your thoughts. Is there any place where I can use this? 
Attachment

pgadmin-hackers by date:

Previous
From: Nikhil Mohite
Date:
Subject: [pgadmin-org/pgadmin4] be4db5: Fixed an issue where PSQL tool not working if the ...
Next
From: Dave Page
Date:
Subject: Re: Regarding feature #6367 "DROP DATABASE can now take the option FORCE ..."