From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
---|---|
To: | <josh(at)agliodbs(dot)com> |
Cc: | <pgadmin-hackers(at)postgresql(dot)org>, "Andreas Pflug" <pgadmin(at)pse-consulting(dot)de> |
Subject: | Re: Possible issue in pgAdmin regarding varchar adjustment |
Date: | 2004-11-09 08:41:46 |
Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4307065@ratbert.vale-housing.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
> -----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?
Regards, Dave
From | Date | Subject | |
---|---|---|---|
Next Message | cvs | 2004-11-09 12:49:15 | CVS Commit by dpage: Install core in proper location |
Previous Message | Joachim Wieland | 2004-11-08 23:26:43 | compile report |