Skip to content
This repository has been archived by the owner on Sep 15, 2022. It is now read-only.

Query output is misleading due to grid cell size (RM #619) #390

Open
dpage opened this issue Aug 26, 2012 · 2 comments
Open

Query output is misleading due to grid cell size (RM #619) #390

dpage opened this issue Aug 26, 2012 · 2 comments
Labels

Comments

@dpage
Copy link
Contributor

dpage commented Aug 26, 2012

Issue migrated from Redmine: https://redmine.postgresql.org/issues/619
Originally created by Anonymous at 2012-08-26 06:24:53 UTC.

Running the latest trunk build (g7ac0c60)

When pgAdmin displays the query output in a grid each column seems to be sized based on the header size and the value is truncated as needed. There is no indication that it's been truncated. This sometimes makes the result highly misleading and I've just spent 5-10 minutes scratching my head about why a function is returning such a strange result!

Here's what the output looked like: http://i48.tinypic.com/5fkdmp.png... but resizing the cell shows something very different: http://i47.tinypic.com/2ennsqv.png

I would suggest that pgAdmin:

  1. Always truncate the end of the string, not the start
  2. Show some indication that the string has been truncated, eg. append "..." or show some subtle overlay with a wavy line - as long as there's something.
  3. For numeric types make the column wide enough to always show at least the part before the decimal point (or, for integer types, the entire number).
@dpage
Copy link
Contributor Author

dpage commented Aug 26, 2012

Comment migrated from Redmine: https://redmine.postgresql.org/issues/619#note-1
Originally created by Guillaume Lelarge at 2012-08-26 08:00:08 UTC.

Items 1 and 2 seem enough.

@dpage
Copy link
Contributor Author

dpage commented Aug 26, 2012

Comment migrated from Redmine: https://redmine.postgresql.org/issues/619#note-2
Originally created by Anonymous at 2012-08-26 09:37:46 UTC.

Thanks for adding this. 1 and 2 together should be enough - 3 is a nice-to-have. I'd say that at least 1 should be high priority. It's not just a matter of convenience - the query output, as shown, is actually "incorrect". Yes, you can make it correct if you know how, but most people won't, especially if previous versions didn't do this.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

1 participant