You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 15, 2022. It is now read-only.
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!
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 freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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:
The text was updated successfully, but these errors were encountered: