From: Basil Bourque <basil.bourque.lists@pobox.com>
To: pgadmin-support@postgresql.org
Sent: Saturday, January 7, 2012 11:30 PM
Subject: Re: [pgadmin-support] Column not wide enough for data
>>>> I expanded the column and discovered the
>>>> actual count
>>>> Is there a way to tell
>>>> PgAdmin to expand the column to fit the data?
>>>
>>> No, there's no such option. If you resize the column afterwards, and
>>> then rerun the query, it'll keep the new column size. But right now,
>>> it's not smart enough to guess the width of the column. I suppose we
>>> don't do it yet because it would take a long time to do if you have a
>>> big number of rows and/or a big number of columns. We should probably
>>> revisit that.
>> I understand the problem that a large number of rows imposes on sizing
>> the column to fit the data. Here is an alternative that is much easier
>> to implement. By default, PgAdmin appears to allocate a fixed, equal
>> column width to all columns. If the total width of all columns is less
>> than the display window, then divide the display window width by the
>> number of columns, and apply that equal width to all columns. So if a
>> query produces a small number of columns, then they can be sized to fill
>> the display window. In my case, with only a count result, the one
>> column would fill the entire width.
>
> That's an interesting idea. Not sure how much helpful wxWidgets will be
> with your idea, but it will be easy to check.
Another approach taken by other tools is to scan a small number of the rows to find the widest value. Say, the first 10 or 200 rows. Or whatever number seems reasonable.
--Basil Bourque
--
Sent via pgadmin-support mailing list (
pgadmin-support@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgadmin-support