Re: ALTER TABLE & COLUMN - Mailing list pgsql-general

From Tino Wildenhain
Subject Re: ALTER TABLE & COLUMN
Date
Msg-id 3955377.1038829098@liza
Whole thread Raw
In response to Re: ALTER TABLE & COLUMN  (Çagil Seker <cagils@biznet.com.tr>)
Responses Re: ALTER TABLE & COLUMN
List pgsql-general
Hi Cagil,

--On Montag, 2. Dezember 2002 09:13 +0200 Çagil Seker
<cagils@biznet.com.tr> wrote:

>> -----Original Message-----
>> From: Christoph Dalitz [mailto:christoph.dalitz@hs-niederrhein.de]
>>
>> Date: 29 Nov 2002 15:22:06 -0500
>> From: Neil Conway <neilc@samurai.com>
>> >
>> > > I am surprised by the fact that altering tables and columns is so
>> > > limited in PostgreSQL, this powerful DBMS! Changing
>> column types and
>> > > droping columns are missing important features I think.
>> >
>> Actually this seems to be one of the rare areas where MySQL is better.
>> PG 7.3 improves a lot though.

Without triggers and referential integrity, changing columns is a
lot easyer ;)

> I've started a new project a few weeks ago. I had to make a choice
> between these two dbs. Just because table and column administration is
> difficult on PG, I chose MySQL (although I'd found PG better on all other
> areas). Then at that time PG 7.3 comes out and solves at least some of
> the problems! What a coincedence! Now I will switch to PG.

... *snip* ...

> That's a huge problem really, not a syntactic sugar, otherwise more of a
> syntactic salt :) I want some of my users (not all are db admin) to be
> able to alter tables with pgAdmin. How can I expect them to achieve those
> N-step voodoo as it will be seen to them?

I dont think its wise to make regular changes to your table structure.
Let alone these changes are made by untrained people.

Regards
Tino

pgsql-general by date:

Previous
From: Jochem van Dieten
Date:
Subject: Re: Renaming schema's [SOLVED]
Next
From: Diogo Biazus
Date:
Subject: Portuguese translation of the press release