From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | Chris Velevitch <chris(dot)velevitch(at)gmail(dot)com>, pgadmin-support(at)postgresql(dot)org |
Subject: | Re: [1.4rc1] Can't change column type |
Date: | 2005-11-09 11:35:56 |
Message-ID: | 4371DF1C.3020409@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
Dave Page wrote:
>
>
> On 6/11/05 9:11 am, "Chris Velevitch" <chris(dot)velevitch(at)gmail(dot)com> wrote:
>
>
>>On 11/6/05, Sim Zacks <sim(at)compulab(dot)co(dot)il> wrote:
>>
>>>However, if your main database activity is changing the data type of a
>>>column in ways that are disallowed by PostGreSQL, then you are
>>>correct. PGAdmin is pointless.
>>
>>My main database activity is refactoring and version control of a
>>database. This activity should be supported by a tool like pgAdmin.
>
>
> It is, or at least it was. It looks like you just found the first bug in
> 1.4.0 :-(
Well, this is not a really bug but an incompletely supported pgsql8.x
feature; 1.4 works the same way as 1.2.
We're allowing only binary compatible type changes (from pre 8.0 ages
where we did type changes by direct catalog access), while with 8.x
castable changes are allowed. We must have missed that in the 7.5 cycle.
Changed in svn for 1.4.1 and HEAD now, thanks for reporting.
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Pflug | 2005-11-09 11:37:48 | Re: [1.4rc1] Can't rename constraint |
Previous Message | Andreas Pflug | 2005-11-09 10:27:47 | Re: Procedure editing bug |