From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>, "Bradley Baetz" <bbaetz(at)student(dot)usyd(dot)edu(dot)au> |
Cc: | <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [INTERFACES] [pgaccess-users] RE: bugzilla.pgaccess.org |
Date: | 2002-07-11 02:13:31 |
Message-ID: | GNELIHDDFBOCMGBFGEFOIEBDCDAA.chriskl@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > Note that before bugzilla really supports postgresql, we (ie
> the bugzilla
> > team) are going to need DROP COLUMN support, as well as support for
> > changing a field's type. This is because thats how upgrades are
> done, when
> > new features change the bz schema.
>
> DROP COLUMNS should be in 7.3, due out in the Fall.
Assuming, of course, that I can get past these latest problems that Tom
brought up - otherwise I guess I could pass it off again :(
> You can simulate
> ALTER COLUMN by creating a new column, UPDATING the data to the new
> column, dropping the old, then renaming the new column to the old name.
Well, once DROP COLUMN is natively supported, I intend to implement a SET
TYPE or MODIFY function - it should be quite straightforward once DROP
COLUMN is done. It will maintain all foreign key and index references
properly...
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Rod Taylor | 2002-07-11 02:18:19 | Re: [INTERFACES] [pgaccess-users] RE: |
Previous Message | Bruce Momjian | 2002-07-11 02:07:48 | Re: [INTERFACES] [pgaccess-users] RE: bugzilla.pgaccess.org |