Re: [HACKERS] What can we learn from MySQL? - Mailing list pgsql-advocacy

From Jeff Davis
Subject Re: [HACKERS] What can we learn from MySQL?
Date
Msg-id 1082708197.32307.1136.camel@jeff
Whole thread Raw
In response to Re: What can we learn from MySQL?  (Christopher Kings-Lynne <chriskl@familyhealth.com.au>)
List pgsql-advocacy
> I have already told Bruce at length about the single most common
> complaint in the phpPgAdmin lists and in the IRC channel: the inability
> to change column types.  I think we should listen to the punters on that
> one.
>

Maybe a simple and less dangerous option would be to add a column of the
new type, rename the old column and hide it, and select from the old
column and cast it to the new column? Is that a feasible implementation?
If I really need to change a column, that's what I'd do.

It's certainly less dangerous than MySQL. I remember a horror story
watching my column silently cast itself to a bunch of blank values in
MySQL. In postgres you'd just be able to undo it or fix the problem
since the data is still there. I also understand that MySQL has to copy
the entire table or something insane like that, so we could use the
opportunity to brag about how much more efficient we are for large
tables.

    Regards,
        Jeff Davis


pgsql-advocacy by date:

Previous
From: Jeff Davis
Date:
Subject: Re: What can we learn from MySQL?
Next
From: Francois Suter
Date:
Subject: Re: What can we learn from MySQL?