Thread: Re: [CYGWIN] Requirement for pgAdmin browser.

> -----Original Message-----
> From: Bruce Momjian [mailto:pgman@candle.pha.pa.us]
> Sent: 15 December 2001 18:06
> To: jm.poure@freesurf.fr
> Cc: pgsql-hackers@postgresql.org; pgsql-cygwin@postgresql.org
> Subject: Re: [HACKERS] [CYGWIN] Requirement for pgAdmin browser.
>
> > PostgreSQL does not allow table modification. The community
> have been
> > waiting
> > for an ALTER TABLE DROP COLUMN and type PROMOTION /
> DEMOTION, for a long
> > time. Same as for Views and triggers : it is impossible to
> alter them... The
> > politics of PostgreSQL is to offer advanced features before
> basic ones.
> >
> > Is anyone working seriously on those issues?
>
> Agreed.  We couldn't decide the best way to do it, so we did
> nothing.  I have hopes for 7.3.

This is starting to become an issue for me. Personally I can live without
these features (though I'd rather not) because I know how to do these things
manually, however many pgAdmin users cannot (without help/pointing in the
right direction). Since I rewrote pgAdmin as pgAdmin II, the program is that
much more stable and easy to use (blowing my own trumpet somewhat!!) that
probably the most common support question I get asked these days is 'how do
I drop a column?'.

I don't want to try to pressure the developers on this as I know what that's
like myself, but this issue is imho *really* beginning to hold PostgreSQL
back from being less of a hackers database and more commonly used like M$
SQL (which though evil _is_ easy to use :-) ).

Regards, Dave.

> This is starting to become an issue for me. Personally I can live without
> these features (though I'd rather not) because I know how to do these things
> manually, however many pgAdmin users cannot (without help/pointing in the
> right direction). Since I rewrote pgAdmin as pgAdmin II, the program is that
> much more stable and easy to use (blowing my own trumpet somewhat!!) that
> probably the most common support question I get asked these days is 'how do
> I drop a column?'.
>
> I don't want to try to pressure the developers on this as I know what that's
> like myself, but this issue is imho *really* beginning to hold PostgreSQL
> back from being less of a hackers database and more commonly used like M$
> SQL (which though evil _is_ easy to use :-) ).

Yes.  Sometimes we can't decide so we do nothing in hopes a better
solution will emerge.  In some cases, such a solution does not exist and
we have to just do our best to implement these missing features.

--
  Bruce Momjian                        |  http://candle.pha.pa.us
  pgman@candle.pha.pa.us               |  (610) 853-3000
  +  If your life is a hard drive,     |  830 Blythe Avenue
  +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026