Unfortunately, some of the head aches I have been encountering require me to
be able to do such oddities (example: my money column type not working with
the pgsql odbc driver). It's not just limited to a varchar to int
conversion that was just an example. There's a bunch of things that I need
to be able to do (and I would gladly help with the coding if I knew where to
start).
Geoff
-----Original Message-----
From: mlw [mailto:markw@mohawksoft.com]
Sent: Monday, September 24, 2001 9:25 PM
To: Gowey, Geoffrey
Cc: 'Alex Pilosov'; pgsql-hackers@postgresql.org
Subject: Re: Changing data types
"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.