Thats fair. The ability to rollback most changes isn't overly useful.
What is useful is the ability to replay commands on another database.
I suggest a good replacement would be a simple 'log' mode which writes
text based queries to a log file. PGAdmin should be able to play an
arbitrary text file against a database connection. This would
preserve most of the functionality and should be straight forward to
implement. The only catch is it shouldn't have the select queries in
it which the PGAdmin uses to determine structure.
--
Rod
----- Original Message -----
From: "Dave Page" <dpage@vale-housing.co.uk>
To: <pgadmin-hackers@postgresql.org>; <pgadmin-support@postgresql.org>
Sent: Wednesday, May 01, 2002 5:09 PM
Subject: [pgadmin-hackers] RFC: Removal of Revision Control
> I am in the process of making *major* changes to the pgAdmin code to
> support Schemas in the upcoming PostgreSQL 7.3 release.
>
> I would like to remove the Revision Control feature from pgAdmin 1.3
for
> the following reasons:
>
> 1) It is difficult to maintain. Removing the code will make Schema
> implementation significantly easier.
>
> 2) It is of limited use (for example, rolling back a table will lose
its
> data, rolling back other objects like functions or views may break
> functions, views, triggers, indexes etc that are dependant on that
> object).
>
> 3) It isn't particuarly reliable. RC Status is often reported
> incorrectly.
>
> 4) I suspect few, if any users actually make use of the feature
> (including myself!).
>
> Does anyone have any objections or comments?
>
> Regards, Dave.
>
> ---------------------------(end of
broadcast)---------------------------
> TIP 2: you can get off all lists at once with the unregister command
> (send "unregister YourEmailAddressHere" to
majordomo@postgresql.org)
>