From: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | "'jochen(dot)westland(at)be-call(dot)de'" <jochen(dot)westland(at)be-call(dot)de>, "'pgadmin-support(at)postgresql(dot)org'" <pgadmin-support(at)postgresql(dot)org> |
Subject: | Re: Feedback to pgadmin II |
Date: | 2001-12-18 13:07:44 |
Message-ID: | FED2B709E3270E4B903EB0175A49BCB104738A@dogbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
> -----Original Message-----
> From: Jochen Westland [mailto:jochen(dot)westland(at)be-call(dot)de]
> Sent: 18 December 2001 12:20
> To: 'pgadmin-support(at)postgresql(dot)org'
> Subject: [pgadmin-support] Feedback to pgadmin II
>
>
> Hi there,
> first of all i'd like to say that pgadmin II seems to be a
> great piece of work done by the development team, thanks to
> all of you.
Hi, glad you like it.
> I have some suggestions for further releases maybe:
>
> 1.) Data modelling tool
> I would love a feature for data-modelling without direkt
> database-sided execution just for modelling purposes.
To be honest, this is unlikely to happen unless someone volunteers to do it.
> 2.) support of database-creation-scripts for pgsql
> I'd be very thankful for a feature like pg_dumpall for
> duplicating database structures out of pgadmin,
File -> Save DB Schema
Note that this should definitely *not* be used as a backup tool though - use
pg_dump for this.
> and a feature
> for importing those scipts into pgadmin as well.
Click the SQL button, and load a previously created script. pgAdmin doesn't
support \connect directives though, so watch out for that.
> 3.) server sided objects of pg_admin I
> Sadly i'm not able to run pgadmin I anymore and
> now have to delete all server sided objects of pgadmin I
> by hand. A Tool for all pgadmin I users to remove
> those objects would be very very suitable.
Should be fairly easy. If I get a bored 5 minutes I'll knock up a plugin.
> 4.) Cross server database access
> I'd like to access databases on several servers
> in one session
That's *very* difficult to do. The whole object model on which the code is
written is based aound the concept of a single server.
>
> 5.) Cross database data model mirroring
> A tool migrating data models from one database
> ( a development system maybe) to another system
> ( a life system maybe) would be very handy for me as
> well :)
Check out the Publishing Wizard. It allows you to publish selected (or all)
objects from one database to any number of target databases. It can attempt
to drop objects before creating them, and gives an option to reset
sequences. It doesn't handle data though.
Hth, regards, Dave.
From | Date | Subject | |
---|---|---|---|
Next Message | Timon Meyer | 2001-12-18 14:41:09 | Problems changing type of column using pgAdmin... |
Previous Message | Jochen Westland | 2001-12-18 12:19:33 | Feedback to pgadmin II |