Re: Table modification

> -----Original Message-----
> From: Jean-Michel POURE [mailto:jm(dot)poure(at)freesurf(dot)fr]
> Sent: 02 October 2001 21:30
> To: pgadmin-hackers(at)postgresql(dot)org
> Subject: Re: [pgadmin-hackers] Table modification
>
>
>
> >OK, following some tests I find that PostgreSQL doesn't validate a
> >PL/pgSQL function when it builds it as I thought. I tend to
> use plain
> >SQL functions which are validated so the situation you
> describe above
> >cannot occur. That is why I figure that the best validation is to
> >actually build each object.
>
> I did this test: create functionA based on functionB, drop functionB,
> create functionB.
> functionA is not broken. Things are much more easy than I
> thought !!!!!
>
> No need to use development tables for functions !!!!!
> OK, I admit there are serious **holes** in my point of view.

Ahh, so we're both a bit wrong! I thought it was just me...

Right, my suggestion is this:

Let me finish Revision Control, then take a look at what it does. It *will*
be a useful system to some people, however, it might not be what you
require. It might be easier then to figure out how to add what you require.

I have now added (in CVS) a Commit option to allow committing of changes
made outside pgAdmin, and a History viewer. This History Viewer will include
the Rollback option, but that's not there just yet. Currently these options
are on the right click menu.

I have tomorrow off work and the house to myself so I should be able to
finish the rcs then.

Good night,

Dave.