Bug: Delete row no longer working

[jurgisk]

Describe the bug

Describe the bug
Since the latest version implemented the delete statements (when you right click to delete a row when you have run a query like this "SELECT * FROM blaa" are no longer deleting the entries by primary key.
Instead now the delete query tries to match every single field. And it breaks when dealing with json fields.
I'm running this against postgres database.
So I think really need to go back to the regular mechanism for deleting using primary key only not the full match.

To Reproduce
Steps to reproduce the behavior:

1. Run "SELECT * FROM blaa" on a table that has a populated json field
2. Right click delete row
3. Confirm deletion
4. See error

Expected behavior
Ideally should just delete the row. And ideally as it used to be using primary key only.

Screenshots

Product

SQLPro for Postgres

App version

Version 2026.87 (Build 1047930)

Platform

macOS

Installation source

Website download

[hankinsoft]

Hi,
The 'all column' based deleting should only occur if the primary key detection failed for the table. Did you happen to notice if any columns lighted up blue (primary key detection) when you were doing the delete?

I have made a few changes to the primary key detection that might help solve that and I've also made it so that the WHERE clause will no longer use json or xml fields when performing a match.

I should be able to post the build later this week, just trying to solve a few other things first as well.

[jurgisk]

Not really.
The only thing that gets lighted up blue is the column where I right-click the mouse. But then when the deletion happens, nothing changes. In this example I've right-clicked the third column from left (but it does not change behaviour if I rightclick the first column (primary key in this instance).
Here's a visual.

Really appreciate you picking this up :)
In terms of urgency - not such a big deal really, since I can still craft a delete SQL statement :D