Message-ID: <0f00ec11-f8e7-4688-9580-9206fd9aebdc@darrenduncan.net>
Date: Wed, 16 Jul 2025 00:19:00 -0700
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
To: pgAdmin Support <pgadmin-support@postgresql.org>
Content-Language: en-US
From: Darren Duncan <darren@darrenduncan.net>
Subject: Naming Object commands "Delete" is a source of user errors
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Archived-At: 
 <https://www.postgresql.org/message-id/0f00ec11-f8e7-4688-9580-9206fd9aebdc%40darrenduncan.net>
Precedence: bulk

I am finding that it is a recurring and damaging source of user error that 
Object/Explorer commands named "Delete" actually correspond to SQL DROP rather 
than SQL DELETE or TRUNCATE. Multiple times I have accidentally dropped tables 
when I meant to just truncate them.

I created a GitHub issue requesting to rename the "Delete" commands to "Drop" to 
help avoid this regular source of cognitive dissonance that leads to errors.

https://github.com/pgadmin-org/pgadmin4/issues/8958

I'm also mentioning the issue in this support list to help draw attention to it.

Thank you.

Darren Duncan