Re: [pgadmin-hackers] pgAdmin III commit: Fix the query editor behaviour with COPY

2014-12-05 Thread Guillaume Lelarge
Hi, 2014-12-05 10:46 GMT+01:00 José Pino p...@getyourguide.com: Hi Guillaume, Is it not possible to change this limit? As a user, why I can't define this row limit in 200 or 1000? Most likely because nobody bothered to write a patch for this. Actually, that's the first time I hear someone

[pgadmin-hackers] pgAdmin III commit: Fix the query editor behaviour with COPY

2014-12-05 Thread José Pino
Hi Guillaume, Is it not possible to change this limit? As a user, why I can't define this row limit in 200 or 1000? Thanks for your help. -- *Jose Luis Lopez Pino*

[pgadmin-hackers] pgAdmin III commit: Fix the query editor behaviour with COPY

2012-11-29 Thread Guillaume Lelarge
Fix the query editor behaviour with COPY If you run something like: copy (select * from pg_stat_activity) to stdout; in the query editor, it will hang forever. The code in pgQueryThread::execute() doesn't check for a PGRES_COPY_OUT result, and calls PQgetResult() repeatedly. PQgetResult() will

[pgadmin-hackers] pgAdmin III commit: Fix the query editor behaviour with COPY

2012-11-29 Thread Guillaume Lelarge
Fix the query editor behaviour with COPY If you run something like: copy (select * from pg_stat_activity) to stdout; in the query editor, it will hang forever. The code in pgQueryThread::execute() doesn't check for a PGRES_COPY_OUT result, and calls PQgetResult() repeatedly. PQgetResult() will