I think that feature, plus filling in some of the holes in the object model, like more complete inheritance, would make
PostgresVERY much more useful, not that it isn't today. It just would have awider audience.
Sven Koehler wrote:
> Hi,
>
> one of the biggest disease of PostGreSQL is, that i can't change the definition of a column.
>
> In order to do that, i'd have to drop any keys, drop the column and create a new one with all indexes etc.
>
> Are there any plans to overcome that problem?
> Even simple changes like varchar(20) to varchar(200) are not allowed.
>
> I asked this question about 2 years ago, and there were only some guys, that told me that i wouldn't need to change
myDB f i'd plan it well.
>
> So my DB is planned well, but i have to change it every now and than because i must implement the changes that my
clientdemands me to do, and have some extra work that nobody will pay me for, if there's no way to change a column.
>
> This is the only missing feature, that prevent me to use this DBMS - i'd love to, because it's an ORDBMS and that's
whati'd have needed sometimes.
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql.org
>