Skip site navigation (1) Skip section navigation (2)

[pgAdmin III] #150: Two feature requests for the Graphical Query Builder

From: "pgAdmin Trac" <trac(at)code(dot)pgadmin(dot)org>
To:
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: [pgAdmin III] #150: Two feature requests for the Graphical Query Builder
Date: 2010-03-17 11:31:11
Message-ID: 056.cd19013aad69eb7a0efced92ebe8e8ca@code.pgadmin.org (view raw or flat)
Thread:
Lists: pgadmin-hackers
#150: Two feature requests for the Graphical Query Builder
-----------------------------+----------------------------------------------
 Reporter:  Julius Tuskenis  |       Owner:  dpage
     Type:  feature          |      Status:  new  
 Priority:  minor            |   Milestone:       
Component:  pgadmin          |     Version:  trunk
 Keywords:  gqb              |    Platform:  all  
-----------------------------+----------------------------------------------
 I don't usually use the builder, but sometimes it is convenient for long
 table/column names having queries. I'd like to propose some improvements
 to it:
 1. Why not join the selected tables if they are related over foreign key?
 Usually well designed database uses FK to keep relations in order, so when
 you drop a new table to a query builder window there could be checked if
 the table can be linked to the already used tables in builder.
 2. I think, that  tables should be linked using join statement, not the
 where clause. That way we could have left, right and inner joins easily.

 I think these 2 impovements would make the builder more usable :).

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

pgadmin-hackers by date

Next:From: pgAdmin TracDate: 2010-03-17 11:34:11
Subject: [pgAdmin III] #151: Can't access entire window in Graphical Query Builder (Windows platform)
Previous:From: Ashesh VashiDate: 2010-03-17 10:36:28
Subject: pgAdmin III: Query Window does not give any error, if it does not able to open the given file.

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group