public inbox for [email protected]
help / color / mirror / Atom feedFrom: Jeff Davis <[email protected]>
To: Christopher Kings-Lynne <[email protected]>
Cc: PostgreSQL advocacy <[email protected]>
Subject: Re: [HACKERS] What can we learn from MySQL?
Date: Fri, 23 Apr 2004 01:16:38 -0700
Message-ID: <1082708197.32307.1136.camel@jeff> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
<[email protected]>
> 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
view thread (145+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: [HACKERS] What can we learn from MySQL?
In-Reply-To: <1082708197.32307.1136.camel@jeff>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox