From: | Rohit Bhati <rohit(dot)bhati(at)enterprisedb(dot)com> |
---|---|
To: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Proposal for ticket No :- #7411 |
Date: | 2024-05-02 09:26:26 |
Message-ID: | CABscKVjj5pMEsWV1bkdaHAkKCA2xEDdyr4diEF7=9yxSXXzdJQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Dear Team,
I hope this message finds you well. I'm reaching out to discuss a proposed
enhancement for our project regarding the formatting of deletion actions.
As I've working on GitHub ticket #7411
<https://github.com/orgs/pgadmin-org/projects/1/views/1?filterQuery=rohi&pane=issue&itemId=60811972>,
there's a suggestion to introduce consistent formatting specifically for
the "Delete database force" action. However, upon further review, I believe
extending this formatting to other deletion actions could significantly
improve user clarity and experience.
Here's a summary of the proposed changes:
- Delete database and Table: Click to delete the currently selected
object from the server. (use the same code, if one is made bold, then both
will become bold)
- Delete database force: Click to delete the currently selected database
with the force option. (as per the original suggestion)
- Delete table cascade: Click to delete the currently selected object
and all dependent objects from the server.
- Delete Truncate: Remove all rows from the table.
- Delete Truncate Cascade: Remove all rows from the table and its child
tables. I'd like to gather your thoughts on extending this proposal to
include all mentioned deletion actions.
Please take a moment to review the proposal and share your thoughts,
concerns, or alternative suggestions and I look forward to hearing from you
soon.
Best regards,
Rohit Bhati
From | Date | Subject | |
---|---|---|---|
Next Message | Akshay Joshi | 2024-05-02 10:49:37 | pgAdmin 4 v8.6 Released |
Previous Message | Yogesh Mahajan | 2024-05-02 08:40:43 | Re: pgAdmin4 v8.6 candidate builds |