Thread: Re: [pgadmin-support] Graphical ER Editor / Graphical Query

> > 2. Query Debugger. I reckon this would only be feasible as a
> > cross-development thing with the postmaster boys-and-girls.
>
>This is one of those things that will go a long way to replicating
>PostgreSQLs parser - i.e., masses of work without a huge benefit.
>
>I would suggest a system that uses the existing parser by attempting to
>execute the query, and interpreting any error messages that are returned
>followed by whatever highlighting of the dodgy syntax can be achieved.
>
>The downside of this is that if a large query is OK, then it will be
>executed. It is possible to prevent this by prepending EXPLAIN, but that
>will only work for SELECT queries.

Yes, I had rather assumed that deep in postmaster there must be decisions
made about the syntax and semantics of a query - the issue was whether
there was any way to hook into these decisions as postmaster is making them
and expose them back to the pgAdmin user to interrupt, breakpoint etc. etc.

Tim.

Mark & Others,

Tim again. My thinking about the graphical facilities under discussion here
to do with pgAdmin could start with making an ActiveX control that displays
a table graphic, a la the Access graphical editor.

The control would potentially take something like a reference to a table
from pgSchema?? (I've not looked at pgSchema in any detail yet) and render
the table's fields in a box, showing which are PK, which have constraints,
indexes, foreign keys etc. using mixture of colour, bold, italic etc.

This control can then be used in numerous other places, like in a QBE
editor, a Relational Schema screen and no doubt other places (like the
create table dialogue boxes, as a table is being created...?)

This work would also give a clear goal post of completion - once its
written its usable, and if any of us have to drop out of the race we leave
behind something of worth.

Tim.

Le Mercredi 27 Février 2002 11:20, Tim Finch, FosterFinch Ltd a écrit :
> The control would potentially take something like a reference to a table
> from pgSchema?? (I've not looked at pgSchema in any detail yet) and render
> the table's fields in a box, showing which are PK, which have constraints,
> indexes, foreign keys etc. using mixture of colour, bold, italic etc.

pgSchema is a an object-oriented abstraction layer representing schema
objects. Therefore, there is no need to reference pgSchema tables. All you
need is to call pgSchema objects.

/JMP

This is pretty much where I am at.  I have the basic layout of the SQL
server new view window done.  The resizing code was a pain to implement
cleanly, but I did get it after a spell.

I agree with the need for a custom control for the entity diagrams.  The key
is to make the control powerful enough so that at design time, the
programmer can modify the control to suit their purpose.  For example, the
ideal control for the query planner is not the same as for a relationship
diagram, but they are close enough that it ought to be one customizable
control.  This control also needs to handle views, functions, rules,
triggers, etc (in their appropriate spots).

I am working on such a control now, but I've just barely begun that.

Mark

-----Original Message-----
From: pgadmin-hackers-owner@postgresql.org
[mailto:pgadmin-hackers-owner@postgresql.org]On Behalf Of Tim Finch,
FosterFinch Ltd
Sent: Wednesday, February 27, 2002 2:20 AM
To: pgadmin-hackers@postgresql.org
Subject: [pgadmin-hackers] Graphical ER Editor / Graphical Query Editor :
First stages?

Mark & Others,

Tim again. My thinking about the graphical facilities under discussion here
to do with pgAdmin could start with making an ActiveX control that displays
a table graphic, a la the Access graphical editor.

The control would potentially take something like a reference to a table
from pgSchema?? (I've not looked at pgSchema in any detail yet) and render
the table's fields in a box, showing which are PK, which have constraints,
indexes, foreign keys etc. using mixture of colour, bold, italic etc.

This control can then be used in numerous other places, like in a QBE
editor, a Relational Schema screen and no doubt other places (like the
create table dialogue boxes, as a table is being created...?)

This work would also give a clear goal post of completion - once its
written its usable, and if any of us have to drop out of the race we leave
behind something of worth.

Tim.


---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

>
>pgSchema is a an object-oriented abstraction layer representing schema
>objects. Therefore, there is no need to reference pgSchema tables. All you
>need is to call pgSchema objects.

Thanks, Jean, that's what I was meaning in a funny sort of way.

Tim.

Mark, you seem to be well on the way! Is there anywhere you think I could
get involved?
Dave/Jean is there any way you can set up a sep portion on the CVS where
this semi project can be held, without necessarily giving us rights to
upload the main project files for pgAdmin????
Tim.

At 10:04 27/02/2002 -0800, Mark A. Taff wrote:
>This is pretty much where I am at.  I have the basic layout of the SQL
>server new view window done.  The resizing code was a pain to implement
>cleanly, but I did get it after a spell.
>
>I agree with the need for a custom control for the entity diagrams.  The key
>is to make the control powerful enough so that at design time, the
>programmer can modify the control to suit their purpose.  For example, the
>ideal control for the query planner is not the same as for a relationship
>diagram, but they are close enough that it ought to be one customizable
>control.  This control also needs to handle views, functions, rules,
>triggers, etc (in their appropriate spots).
>
>I am working on such a control now, but I've just barely begun that.
>
>Mark
>
>-----Original Message-----
>From: pgadmin-hackers-owner@postgresql.org
>[mailto:pgadmin-hackers-owner@postgresql.org]On Behalf Of Tim Finch,
>FosterFinch Ltd
>Sent: Wednesday, February 27, 2002 2:20 AM
>To: pgadmin-hackers@postgresql.org
>Subject: [pgadmin-hackers] Graphical ER Editor / Graphical Query Editor :
>First stages?
>
>Mark & Others,
>
>Tim again. My thinking about the graphical facilities under discussion here
>to do with pgAdmin could start with making an ActiveX control that displays
>a table graphic, a la the Access graphical editor.
>
>The control would potentially take something like a reference to a table
>from pgSchema?? (I've not looked at pgSchema in any detail yet) and render
>the table's fields in a box, showing which are PK, which have constraints,
>indexes, foreign keys etc. using mixture of colour, bold, italic etc.
>
>This control can then be used in numerous other places, like in a QBE
>editor, a Relational Schema screen and no doubt other places (like the
>create table dialogue boxes, as a table is being created...?)
>
>This work would also give a clear goal post of completion - once its
>written its usable, and if any of us have to drop out of the race we leave
>behind something of worth.
>
>Tim.
>
>
>---------------------------(end of broadcast)---------------------------
>TIP 6: Have you searched our list archives?
>
>http://archives.postgresql.org