Re: pgadmin3: present and future

From: "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk>
To: "Andreas Pflug" <Andreas(dot)Pflug(at)web(dot)de>, <pgadmin-hackers(at)postgresql(dot)org>, "Keith" <efesar(at)nmia(dot)com>
Subject: Re: pgadmin3: present and future
Date: 2003-04-01 12:10:43
Message-ID: 03AF4E498C591348A42FC93DEA9661B885F9@mail.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

> -----Original Message-----
> From: Andreas Pflug [mailto:Andreas(dot)Pflug(at)web(dot)de]
> Sent: 01 April 2003 00:20
> To: pgadmin-hackers(at)postgresql(dot)org; Tom Lane; Keith
> Subject: [pgadmin-hackers] pgadmin3: present and future
>
>
> *** Missing, currently I don't plan to implement (and no
> tool, editing a
> xrc file with a text editor isn't that fun):

No it's not :-). Actually I use XRCed which is written in wxPython.
Found it somewhere on the wxWindows site. It's a bit quirky, but once
you get the hang of it it works well.

> - object property dialogs
> - create object dialogs

These are one and the same in pga2, the behaviour is modified based on
whether an existing object is passed to the form.

>
> *** Enhancements I'm thinking of right now (coming soon):
> - split PG_FUNCTIONS into PT_FUNCTIONS AND PG_TRIGGERFUNCTIONS under
> PG_SCHEMA
> - show PG_TRIGGERFUNCTION under PG_TRIGGER

Not sure what you mean by this. Do you mean you want to move functions
with a return type of TRIGGER to somewhere under the Triggers node?

> - attempt to format CREATE VIEW output

This would *definately* be easier to implement in PostgreSQL <shudders
at the thought of writing another SQL parser>. I'll post a message to
the hackers list...

Regards, Dave.

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Dave Page 2003-04-01 12:23:13 Re: pgadmin3 query tools
Previous Message Dave Page 2003-04-01 12:04:06 Re: pgadmin3 query tools