public inbox for [email protected]
help / color / mirror / Atom feedNaming Object commands "Delete" is a source of user errors
4+ messages / 2 participants
[nested] [flat]
* Naming Object commands "Delete" is a source of user errors
@ 2025-07-16 07:19 Darren Duncan <[email protected]>
2025-07-16 07:38 ` Re: Naming Object commands "Delete" is a source of user errors Ray O'Donnell <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Darren Duncan @ 2025-07-16 07:19 UTC (permalink / raw)
To: pgadmin-support
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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Naming Object commands "Delete" is a source of user errors
2025-07-16 07:19 Naming Object commands "Delete" is a source of user errors Darren Duncan <[email protected]>
@ 2025-07-16 07:38 ` Ray O'Donnell <[email protected]>
2025-07-16 07:48 ` Re: Naming Object commands "Delete" is a source of user errors Darren Duncan <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Ray O'Donnell @ 2025-07-16 07:38 UTC (permalink / raw)
To: Darren Duncan <[email protected]>; pgadmin-support
On 16 July 2025 08:19:09 Darren Duncan <[email protected]> wrote:
> 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.
In fairness, you don't (SQL) DELTE tables - you delete their rows, hence
the command is DELETE FROM. And it is intuitive that when you right-click
on an object and click "Delete", it is the object itself which gets zapped.
Also, TRUNCATE is there in the menu too.
Having said that, I recall that the menu used to say "Drop" rather than
"Delete", which IMHO is clearer to SQL-savvy people.... it got changed at
some point.
Ray.
>
> 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
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Naming Object commands "Delete" is a source of user errors
2025-07-16 07:19 Naming Object commands "Delete" is a source of user errors Darren Duncan <[email protected]>
2025-07-16 07:38 ` Re: Naming Object commands "Delete" is a source of user errors Ray O'Donnell <[email protected]>
@ 2025-07-16 07:48 ` Darren Duncan <[email protected]>
2025-07-18 12:50 ` Re: Naming Object commands "Delete" is a source of user errors Darren Duncan <[email protected]>
0 siblings, 1 reply; 4+ messages in thread
From: Darren Duncan @ 2025-07-16 07:48 UTC (permalink / raw)
To: [email protected]
On 2025-07-16 12:38 a.m., Ray O'Donnell wrote:
> On 16 July 2025 08:19:09 Darren Duncan wrote:
>
>> 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.
>
> In fairness, you don't (SQL) DELTE tables - you delete their rows, hence the
> command is DELETE FROM. And it is intuitive that when you right-click on an
> object and click "Delete", it is the object itself which gets zapped. Also,
> TRUNCATE is there in the menu too.
Yes, (SQL) DELETE does not remove the table objects themselves, just the rows in
them, hence the problem that users would see "Delete" in the pgAdmin menus and
choose it instinctively thinking that removing just records is what would happen.
While Truncate is also in the menus, it is further down and often missed when
one sees Delete and thinks that's what I want and stops reading further.
> Having said that, I recall that the menu used to say "Drop" rather than
> "Delete", which IMHO is clearer to SQL-savvy people.... it got changed at some
> point.
And SQL-savvy people are the primary user base of pgAdmin I would assume.
Best for this command to line up to avoid confusion of the same term being used
for 2 very different meanings.
Following a renaming to Drop it should be very easy and quick for people to
adapt to.
Those that don't have the cognitive dissonance would still recognize what the
command does.
IMPORTANT: Alphabetically, Drop and Delete are about in the same positions in
each menu, so those wondering where Delete went would see the similar-appearance
Drop in the same place and should infer through English if not SQL that it does
the same thing.
Darren Duncan
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: Naming Object commands "Delete" is a source of user errors
2025-07-16 07:19 Naming Object commands "Delete" is a source of user errors Darren Duncan <[email protected]>
2025-07-16 07:38 ` Re: Naming Object commands "Delete" is a source of user errors Ray O'Donnell <[email protected]>
2025-07-16 07:48 ` Re: Naming Object commands "Delete" is a source of user errors Darren Duncan <[email protected]>
@ 2025-07-18 12:50 ` Darren Duncan <[email protected]>
0 siblings, 0 replies; 4+ messages in thread
From: Darren Duncan @ 2025-07-18 12:50 UTC (permalink / raw)
To: [email protected]
As a follow-up...
Thank you very much to Akshay Joshi for quickly claiming the GitHub issue I
filed and implementing the fix, and to Anil Sahoo for testing it, seemingly all
in time for the very next pgAdmin 9.6 release, and within about 48 hours of my
request on GitHub.
Darren Duncan
On 2025-07-16 12:48 a.m., Darren Duncan wrote:
> On 2025-07-16 12:38 a.m., Ray O'Donnell wrote:
>> On 16 July 2025 08:19:09 Darren Duncan wrote:
>>
>>> 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.
>>
>> In fairness, you don't (SQL) DELTE tables - you delete their rows, hence the
>> command is DELETE FROM. And it is intuitive that when you right-click on an
>> object and click "Delete", it is the object itself which gets zapped. Also,
>> TRUNCATE is there in the menu too.
>
> Yes, (SQL) DELETE does not remove the table objects themselves, just the rows in
> them, hence the problem that users would see "Delete" in the pgAdmin menus and
> choose it instinctively thinking that removing just records is what would happen.
>
> While Truncate is also in the menus, it is further down and often missed when
> one sees Delete and thinks that's what I want and stops reading further.
>
>> Having said that, I recall that the menu used to say "Drop" rather than
>> "Delete", which IMHO is clearer to SQL-savvy people.... it got changed at some
>> point.
>
> And SQL-savvy people are the primary user base of pgAdmin I would assume.
>
> Best for this command to line up to avoid confusion of the same term being used
> for 2 very different meanings.
>
> Following a renaming to Drop it should be very easy and quick for people to
> adapt to.
>
> Those that don't have the cognitive dissonance would still recognize what the
> command does.
>
> IMPORTANT: Alphabetically, Drop and Delete are about in the same positions in
> each menu, so those wondering where Delete went would see the similar-appearance
> Drop in the same place and should infer through English if not SQL that it does
> the same thing.
>
> Darren Duncan
>
>
>
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2025-07-18 12:50 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2025-07-16 07:19 Naming Object commands "Delete" is a source of user errors Darren Duncan <[email protected]>
2025-07-16 07:38 ` Ray O'Donnell <[email protected]>
2025-07-16 07:48 ` Darren Duncan <[email protected]>
2025-07-18 12:50 ` Darren Duncan <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox