From: | mlw <markw(at)mohawksoft(dot)com> |
---|---|
To: | "Gowey, Geoffrey" <ggowey(at)rxhope(dot)com> |
Cc: | "'Alex Pilosov'" <alex(at)pilosoft(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Changing data types |
Date: | 2001-09-25 01:25:10 |
Message-ID: | 3BAFDCF6.44609287@mohawksoft.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers pgsql-hackers |
"Gowey, Geoffrey" wrote:
>
> >This is not for -hackers.
>
> How so?
>
> >And the answer is "no, you can't". Recreate the table with correct types
> >and insert the old values into it.
>
> You're kidding me, right? *prepares to gargle* MS Sql server can. Surely
> we can implement this feature or aren't we aiming to go head to head with
> commercial rdbms'?
To be honest I am very surprised that MS SQL supports that, but then again
Microsoft is so used to doing everything so utterly wrong, they have to design
all their products with the ability to support fundamental design error
corrections on the fly.
I would be surprised if Oracle, DB2, or other "industrial grade" databases
could do this. Needing to change a column from a varchar to an integer is a
huge change and a major error in design.
Adding a column, updating a column with a conversion routine, dropping the old
column, and renaming the new column to the old column name is probably
supported, but, geez, I have been dealing with SQL for almost 8 years and I
have never needed to do that.
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Pilosov | 2001-09-25 01:41:44 | Re: Changing data types |
Previous Message | Dave Page | 2001-09-24 21:43:49 | Major Update Commited |
From | Date | Subject | |
---|---|---|---|
Next Message | Alex Pilosov | 2001-09-25 01:41:44 | Re: Changing data types |
Previous Message | Tatsuo Ishii | 2001-09-25 00:56:36 | Re: Unicode combining characters |