The row number in result grid is deceptive and easy to lead mistake in data operation

[xzer]

The row number in result grid is deceptive and easy to lead mistake in data operation

[xzer]

I report this as a bug rather than feature request, because this defect has significant impact on data operation correctness.

It should be treated as UI design defect.

[adityatoshniwal]

@xzer You can check any sql editor, all have row numbers because it is very useful in most cases. Your request is first of a kind, no one had a problem with this before. So we're taking it as feature request to allow disabling the rownumbers.

[xzer]

check the dbeaver

https://dbeaver.io/wp-content/uploads/2018/03/data_edit-450x220.png

Yes, it also has row number in the result grid, but it is in clear different cell style and background color, it is very clearly indicate the number is not a part of the data. But look above picture I pasted, they are almost same.

I would say, it may be not necessary to really "hide" it, but it need to be clearly differentiated from the data cells.

[adityatoshniwal]

check the dbeaver

https://dbeaver.io/wp-content/uploads/2018/03/data_edit-450x220.png

Yes, it also has row number in the result grid, but it is in clear different cell style and background color, it is very clearly indicate the number is not a part of the data. But look above picture I pasted, they are almost same.

I would say, it may be not necessary to really "hide" it, but it need to be clearly differentiated from the data cells.

Yes that can be done as well. Right now we add slight shadow to the right edge of row number.

[xzer]

Right now we add slight shadow to the right edge of row number.

If you go back to check my pasted screenshot, I don't think the "slight shadow" can be easily differentiate from other cell border lines.

I was not using postgre and pgAdmin for several years, and I didn't remember I have any trouble on the UI previously, but this time it is really becoming a "bug" to me as I really picked wrong id numbers many times....

I think this is a recent (years?) UI change, and it is not a correct design decision, so I insist this should be treated as a bug rather than feature request.