On Sun, 2012-01-08 at 03:52 -0800, Francisco Leovey wrote:
> Another way of doing it is to generate an HTML popup and let the browser
> decide the WIDTH of each column -
>
> Using "table", "tr" and "td" the width is managed automaticaly or defining
> width as a %
>
Thanks for the idea, but no
n-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 t
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,
On Mon, 2012-01-02 at 21:29 -0500, Guy Rouillier wrote:
> On 1/2/2012 4:40 PM, Guillaume Lelarge wrote:
> > On Tue, 2011-12-20 at 22:29 -0500, Guy Rouillier wrote:
> >> I wanted to copy a table to another table, so I started by getting a
> >> count of the rows in the source table. The result of "s
On 1/2/2012 4:40 PM, Guillaume Lelarge wrote:
On Tue, 2011-12-20 at 22:29 -0500, Guy Rouillier wrote:
I wanted to copy a table to another table, so I started by getting a
count of the rows in the source table. The result of "select count(*)
from " came out like this:
count
bigint
--
26
On Tue, 2011-12-20 at 22:29 -0500, Guy Rouillier wrote:
> I wanted to copy a table to another table, so I started by getting a
> count of the rows in the source table. The result of "select count(*)
> from " came out like this:
>
> count
> bigint
> --
> 26569
>
> Based on that, I concl
I wanted to copy a table to another table, so I started by getting a
count of the rows in the source table. The result of "select count(*)
from " came out like this:
count
bigint
--
26569
Based on that, I concluded that a straightforward "insert into
select * from " would su
