Re: Interesting Issues

From: Dave Page <dpage(at)vale-housing(dot)co(dot)uk>
To: "'Rod Taylor'" <rbt(at)zort(dot)ca>, pgadmin-hackers(at)postgresql(dot)org
Subject: Re: Interesting Issues
Date: 2002-02-11 08:26:33
Message-ID: FED2B709E3270E4B903EB0175A49BCB104754D@dogbert.vale-housing.co.uk
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

> -----Original Message-----
> From: Rod Taylor [mailto:rbt(at)zort(dot)ca]
> Sent: 11 February 2002 02:26
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: [pgadmin-hackers] Interesting Issues
>
>
> PGAdmin doesn't allow a user to create an inherited table
> without additional columns of sometype, as a work around I
> added a nullable single bit column to my table.

No. I don't suppose it's something that many people try to do :-)
Added to TODO.

> Database publishing wizard doesn't remember 'production
> databases' from one time to another.

Added to TODO.

> The historical information (RCS) is quite interesting. Is
> there any chance that the 'Publishing' wizard will be able to
> publish diffs between the database you're publishing to and
> the test version(s)? As a step between these, the ability to
> dump (in SQL form) the difference between one version and
> another (that is, the commands to bring the
> one up to the level with another) would be extreamly useful. Of
> course, both have to be managable without any dataloss.

Unfortunately this is not possible with the current system as the revision
control only stores the SQL to create the object, not what was used to
update it - which might not even be possible if it was modified in a dump
file or by dropping and recreating it.

The only diff we could do would be a traditional text diff which would be
useless.

Regards, Dave.

Responses

Browse pgadmin-hackers by date

  From Date Subject
Next Message Amir Behgooy 2002-02-11 08:30:06 Extending PostgreSQL
Previous Message Rod Taylor 2002-02-11 02:25:45 Interesting Issues