Re: Naming Object commands "Delete" is a source of user errors

2025-07-18 Thread Darren Duncan
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 20

Re: Naming Object commands "Delete" is a source of user errors

2025-07-16 Thread Darren Duncan
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 ha

Re: Naming Object commands "Delete" is a source of user errors

2025-07-16 Thread Ray O'Donnell
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 t

Naming Object commands "Delete" is a source of user errors

2025-07-16 Thread Darren Duncan
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