From: | Bawer Dagdeviren <bawer(at)pucpac(dot)com> |
---|---|
To: | pgadmin-hackers(at)postgresql(dot)org |
Subject: | Re: Changing types without DROP...CASCADE |
Date: | 2006-05-20 21:00:09 |
Message-ID: | 446F8359.9060405@pucpac.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-hackers |
Dave Page wrote:
>
>
>> I think that this particular case is probably not that interesting to
>> most people (though that is not to say it shouldn't be done) - the more
>> common case is already on the TODO list as:
>>
>> - Recreate views after column type change
>>
>> Both are essentially the same problem, and as there may be more similar
>> cases that haven't yet been considered (or may only appear in future
>> releases of PostgreSQL), it seems to me that a relatively generic
>> mechanism for rebuilding dependent objects should be implemented. I
>> don't have time to look at this myself right now, but if you want to
>> please do, and feel free to post any questions you may have.
>>
>> Regards, Dave
Ok, Dave. I will start by looking around in the code-base and get to
know it better. Then I'll try my best to tackle the TODO-entry!
Best wishes,
Bawer
From | Date | Subject | |
---|---|---|---|
Next Message | svn | 2006-05-22 10:14:03 | SVN Commit by dpage: r5172 - in trunk/www: include locale locale/fr_FR locale/fr_FR/LC_MESSAGES |
Previous Message | Dave Page | 2006-05-19 12:27:20 | Re: Changing types without DROP...CASCADE |