Thread: Large tables, copy-and-paste, default sql

Large tables, copy-and-paste, default sql

From
ow
Date:
pgAdmin III, v1.0.0, pgSql 7.4.rc1

Hi,

Thanks for the great product, it really helps!

There a couple of things that, I think, could be improved still:

1. Tree view that shows the list of tables: When I click on a table that
contains relatively large number of rows (20M+), it takes pgAdmin a very, very
long time to show the respective CREATE clause for the table. It appears that
pgAdmin is forcing pgSql to count rows in the table, though I may be wrong. Is
there a way to avoid the delay?

2. pgAdmin Query/Sql tool: It'd be nice if there was a way to copy data from
the "data output" tab. I know it can be exported, but many times I need just a
small piece of data and it'd be nice to just copy-and-paste.

3. pgAdmin Query/Sql tool: IMHO, it be better if Sql/Query tool window opened
blank, i.e. without prepopulating it with SQL of the item that had focus when
Query tool was launched. Most of the time (99%), I remove default SQL, it does
not do me any good.

Thanks






__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree


Re: Large tables, copy-and-paste, default sql

From
"Dave Page"
Date:

> -----Original Message-----
> From: ow [mailto:oneway_111@yahoo.com]
> Sent: 09 November 2003 15:06
> To: pgadmin-support@postgresql.org
> Subject: [pgadmin-support] Large tables, copy-and-paste, default sql
>
> pgAdmin III, v1.0.0, pgSql 7.4.rc1
>
> Hi,
>
> Thanks for the great product, it really helps!
>
> There a couple of things that, I think, could be improved still:
>
> 1. Tree view that shows the list of tables: When I click on a
> table that contains relatively large number of rows (20M+),
> it takes pgAdmin a very, very long time to show the
> respective CREATE clause for the table. It appears that
> pgAdmin is forcing pgSql to count rows in the table, though I
> may be wrong. Is there a way to avoid the delay?

pgAdmin checks the estimated row count before actually counting rows.
You can set the threshold that will prevent counting under
Tools->Options.

> 2. pgAdmin Query/Sql tool: It'd be nice if there was a way to
> copy data from the "data output" tab. I know it can be
> exported, but many times I need just a small piece of data
> and it'd be nice to just copy-and-paste.

You can copy individual values using the normal keysequences such as
Control-C for copy. Currently you cannot select regions of cells for
copy/paste - I'm not sure how feasible this is right now, though I can
see the usefullness of it.

>
> 3. pgAdmin Query/Sql tool: IMHO, it be better if Sql/Query
> tool window opened blank, i.e. without prepopulating it with
> SQL of the item that had focus when Query tool was launched.
> Most of the time (99%), I remove default SQL, it does not do
> me any good.

There is an option to prevent this under Tools->Options.

Regards, Dave.


Re: Large tables, copy-and-paste, default sql

From
Andreas Pflug
Date:
Dave Page wrote:

>>
>>1. Tree view that shows the list of tables: When I click on a 
>>table that contains relatively large number of rows (20M+), 
>>it takes pgAdmin a very, very long time to show the 
>>respective CREATE clause for the table. It appears that 
>>pgAdmin is forcing pgSql to count rows in the table, though I 
>>may be wrong. Is there a way to avoid the delay?
>>    
>>
>
>pgAdmin checks the estimated row count before actually counting rows.
>You can set the threshold that will prevent counting under
>Tools->Options.
>  
>
Please note that there is  a float interpretation problem in 1.0.0 
(7.6e6 -> 7 instead of 7000000), which leads to wrong table size 
estimated values (and thus wrong thresholds for automatic row counting).

Regards,
Andreas




Re: Large tables, copy-and-paste, default sql

From
ow
Date:
--- Dave Page wrote:
> [...]
>
> You can copy individual values using the normal keysequences such as
> Control-C for copy. Currently you cannot select regions of cells for
> copy/paste - I'm not sure how feasible this is right now, though I can
> see the usefullness of it.

That I couldn't do, i.e. it appears that the least I can select in the "data
output" tab is the whole row (can't select a column or a single cell) and
copy-and-paste does not appear to work on rows.

Suspending table counts and default SQL as per File->Options worked fine.

Thanks!













__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree