From: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
---|---|
To: | Dave Page <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | josh(at)agliodbs(dot)com, pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Possible issue in pgAdmin regarding varchar |
Date: | 2004-11-09 15:03:56 |
Message-ID: | 4190DC5C.1010802@pse-consulting.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Dave Page wrote:
>
>
>
>>-----Original Message-----
>>From: Josh Berkus [mailto:josh(at)agliodbs(dot)com]
>>Sent: 09 November 2004 00:47
>>To: Dave Page
>>Subject: Possible issue in pgAdmin regarding varchar adjustment
>>
>>Dave,
>>
>>A user on IRC claims that pgAdminIII allows changing the
>>length of varchar fields, and executes it through updates to
>>pg_attributes and other system
>>tables. If this is incorrect, ignore the rest of this message.
>>
>>The problem with direct updating of pg_attribute in 7.3 and
>>7.4 is that all indexes and views which depend on the table
>>would have to be dropped and
>>re-created. Also, the pg_statistic rows for that column
>>would need to be
>>purged and regenerated. So it seems like a misfeature.
>
>
> Hi Josh,
>
> I'm not entirely sure as I've never really worked on that part of the
> code. Andreas, can you comment on this?
It's correct, and it's on the TODO list as essential. It's clearly a
caveat now (-> FAQ update needed)
Regards,
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | cvs | 2004-11-10 09:41:23 | CVS Commit by andreas: Fix OSX issue |
Previous Message | cvs | 2004-11-09 14:15:45 | CVS Commit by andreas: Fix remembering SSL connection parameter |