Thread: [pgAdmin III] #340: Allow the display of the results of more than one query

#340: Allow the display of the results of more than one query
-----------------------+----------------------------------------------------
 Reporter:  gleu       |       Owner:  dpage
     Type:  feature    |      Status:  new  
 Priority:  minor      |   Milestone:       
Component:  pgadmin    |     Version:  trunk
 Keywords:  querytool  |    Platform:  all  
-----------------------+----------------------------------------------------
 See
 http://pgolub.wordpress.com/2009/11/17/script-slicing-by-pgmdd/ for the
 details

--
Ticket URL: <http://code.pgadmin.org/trac/ticket/340>
pgAdmin III <http://code.pgadmin.org/trac/>
pgAdmin III

Hi,

I  added a new 'psql' ECHO='queriesonlynoexec' on my local machine,
which enables to view multi-statement-query as a list of queries.

I think with this, "pgadmin can execute and display each query  in a
separate tab !


Example:
/home/src/postgresql-devel/build/src/bin/psql/psql --port 5432
--username "postgres" postgres < /tmp/xx.sql > /tmp/xx.log


/tmp/xx.sql
---------------------------
\set ECHO queriesonlynoexec
select 1, '"; Vladimr Kokovic;"';;; select 2; junk !!!;;; select 3;;;


/tmp/xx.log
---------------------------
select 1, '"; vladimr kokovic;"';;; select 2; junk !!!;;; select 3;;;
select 1, '"; vladimr kokovic,"';
;
;
select 2;
junk !!!;
;
;
select 3;
;
;


Best regards,
Vladimir Kokovic, DP senior, Belgrade, Serbia


On 10/2/11, pgAdmin Trac <trac@code.pgadmin.org> wrote:
> #340: Allow the display of the results of more than one query
> -----------------------+----------------------------------------------------
>  Reporter:  gleu       |       Owner:  dpage
>      Type:  feature    |      Status:  new
>  Priority:  minor      |   Milestone:
> Component:  pgadmin    |     Version:  trunk
>  Keywords:  querytool  |    Platform:  all
> -----------------------+----------------------------------------------------
>  See
>  http://pgolub.wordpress.com/2009/11/17/script-slicing-by-pgmdd/ for the
>  details
>
> --
> Ticket URL: <http://code.pgadmin.org/trac/ticket/340>
> pgAdmin III <http://code.pgadmin.org/trac/>
> pgAdmin III
>
> --
> Sent via pgadmin-hackers mailing list (pgadmin-hackers@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgadmin-hackers
>

Hi,

On Sat, 2011-10-08 at 11:28 +0200, Vladimir Kokovic wrote:
> [...]
> I  added a new 'psql' ECHO='queriesonlynoexec' on my local machine,
> which enables to view multi-statement-query as a list of queries.
>
> I think with this, "pgadmin can execute and display each query  in a
> separate tab !
>

I fail to see how this fix the issue. Anyway, we already have a
perfectly clear and simple way to do it. What still is missing is a good
UI.


--
Guillaume
  http://blog.guillaume.lelarge.info
  http://www.dalibo.com

Hi,

When it comes to PQsendQuery and multi-statement-query, it is
necessary to know which is the current query, without a scanner/parser
that's not easy !

Best regards,
 Vladimir Kokovic, DP senior, Belgrade, Serbia

On 10/8/11, Guillaume Lelarge <guillaume@lelarge.info> wrote:
> Hi,
>
> On Sat, 2011-10-08 at 11:28 +0200, Vladimir Kokovic wrote:
>> [...]
>> I  added a new 'psql' ECHO='queriesonlynoexec' on my local machine,
>> which enables to view multi-statement-query as a list of queries.
>>
>> I think with this, "pgadmin can execute and display each query  in a
>> separate tab !
>>
>
> I fail to see how this fix the issue. Anyway, we already have a
> perfectly clear and simple way to do it. What still is missing is a good
> UI.
>
>
> --
> Guillaume
>   http://blog.guillaume.lelarge.info
>   http://www.dalibo.com
>
>

On Sat, 2011-10-08 at 20:25 +0200, Vladimir Kokovic wrote:
> Hi,
>
> When it comes to PQsendQuery and multi-statement-query, it is
> necessary to know which is the current query, without a scanner/parser
> that's not easy !
>

Necessary, no. The results are in the order of the queries. I mean first
tab of results is for the first query, second tab for the second query,
etc. Anyway, we don't need a parser.


--
Guillaume
  http://blog.guillaume.lelarge.info
  http://www.dalibo.com

On Sat, 2011-10-08 at 22:27 +0200, Vladimir Kokovic wrote:
> Hi,
>
> So you think to put in the tab info '13. query of 20 ' instead of  query text ?
>

I don't get what you mean. If you're talking about tabs' titles, I gues
they would "Results #1" for first query, "Results #2" for second query,
etc.

And please, don't top-post. It makes the whole thread hard to read.


--
Guillaume
  http://blog.guillaume.lelarge.info
  http://www.dalibo.com

Hi,

So you think to put in the tab info '13. query of 20 ' instead of  query text ?

Best regards,
  Vladimir Kokovic, DP senior, Belgrade, Serbia

On 10/8/11, Guillaume Lelarge <guillaume@lelarge.info> wrote:
> On Sat, 2011-10-08 at 20:25 +0200, Vladimir Kokovic wrote:
>> Hi,
>>
>> When it comes to PQsendQuery and multi-statement-query, it is
>> necessary to know which is the current query, without a scanner/parser
>> that's not easy !
>>
>
> Necessary, no. The results are in the order of the queries. I mean first
> tab of results is for the first query, second tab for the second query,
> etc. Anyway, we don't need a parser.
>
>
> --
> Guillaume
>   http://blog.guillaume.lelarge.info
>   http://www.dalibo.com
>
>

On Sun, 2011-10-23 at 05:17 +0200, Vladimir Kokovic wrote:
> Hi,
>
> Suppose that each query has its own tab, which has a title, info, and
> the result set, scanner is used to provide info.
>

Sure, I get that. What I'm wondering is "so much code for just that?".
Not worth it in my opinion.


--
Guillaume
  http://blog.guillaume.lelarge.info
  http://www.dalibo.com