> CREATE OR REPLACE VIEW / TRIGGER and ALTER TABLE DROP COLUMN are real
> priorities for us at pgAdmin team
> (http://pgadmin.postgresql.org). I don't
> know PostgreSQL internals, but it should take a few days/weeks to an
> experienced hacker to add these features.
I can see the utility of CREATE OR REPLACE VIEW, however for me the DROP
COLUMN is way more useful. I can't begin to express how annoying it is to
not be able to drop a column. Sooo annoying...
> So why should I do it myself ? We are a community after all. We are not
> working for money but helping each others. If we are bringing
> pgAdmin to a
> large audience, we need more help from hackers on what we
> consider important :
To a certain extent I agree. I have definitely seen times where I have
spent hours and hours and hours of coding doing something that a core
developer can do in no time, but just isn't inclined to do.
As an aside: did anyone read my post about SET NOT NULL? I am happy to
implement this for 7.3, but no-one answered my questions about if it's in
the parser or not, and where to put the code?
> It should be possible to modify or drop any schema object (with a
> priority on
> views, triggers and columns). This is absolute priority for us.
> Can anyone
> help us? Can we make sure it will be added to 7.3? Thanks in advance.
The other side of this is that you are using a completely free product coded
by volunteers. There's no way you can make sure it will be added - all you
can do is to try to convince a developer to implement it. Again, if I sat
down for a week of coding, I might be able to do it, but someone more
familiar with postgres can probably do it in a day...
Chris