From: | Akshay Joshi <akshay(dot)joshi(at)enterprisedb(dot)com> |
---|---|
To: | pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org> |
Subject: | Regarding feature #6367 "DROP DATABASE can now take the option FORCE ..." |
Date: | 2023-06-13 08:35:42 |
Message-ID: | CANxoLDe8jKs8GQN-69jM5SJV6URcJUsr80sG64BbDjUqeeibFQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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:
[image: Properties.png] The 'Drop with Force' button is visible only on
the Databases collection node. For other collection nodes, it is a 'Drop
Cascade'.
[image: Context Menu.png]
Please review and let me know your thoughts. Is there any place where I can
use this?
--
Akshay Joshi
Principal Software Architect
www.enterprisedb.com
*Blog*: https://www.enterprisedb.com/akshay-joshi
*GitHub*: https://github.com/akshay-joshi
*LinkedIn*: https://www.linkedin.com/in/akshay-joshi-086497216
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Page | 2023-06-13 09:20:36 | Re: Regarding feature #6367 "DROP DATABASE can now take the option FORCE ..." |
Previous Message | Nikhil Mohite | 2023-06-13 06:34:39 | [pgadmin-org/pgadmin4] be4db5: Fixed an issue where PSQL tool not working if the ... |