"Hiroshi Inoue" <[EMAIL PROTECTED]> writes:
> My trial implementation using physical/logical attribute numbers
> isn't so clean as I expected. I'm inclined to restrict my change to
> fix the TODO
> * ALTER TABLE ADD COLUMN to inherited table put column in wrong place
> though it would also introduce a backward compatibility.
I'm confused --- how will that make things any simpler or cleaner?
You still need physical/logical column numbering distinction in order
to fix inherited ADD COLUMN, don't you?
regards, tom lane
- RE: AW: [HACKERS] ALTER TABLE DROP COLUMN Hiroshi Inoue
- Re: AW: [HACKERS] ALTER TABLE DROP COLUMN Bruce Momjian
- RE: AW: [HACKERS] ALTER TABLE DROP COLUMN KuroiNeko
- [HACKERS] select oid .... for update .... KuroiNeko
- Re: [HACKERS] select oid .... for update .... Stephan Szabo
- [HACKERS] Permissions, was select oid KuroiNeko
- Re: AW: [HACKERS] ALTER TABLE DROP COLUMN Hiroshi Inoue
- Re: AW: [HACKERS] ALTER TABLE DROP COLUMN Chris
- Re: AW: [HACKERS] ALTER TABLE DROP COLUMN KuroiNeko
- Re: AW: [HACKERS] ALTER TABLE DROP COLUMN Adam Haberlach
- RE: AW: [HACKERS] ALTER TABLE DROP COLUMN Tom Lane
- RE: AW: [HACKERS] ALTER TABLE DROP COLUMN Hiroshi Inoue
- Re: AW: [HACKERS] ALTER TABLE DROP COLUMN Chris
- Re: AW: [HACKERS] ALTER TABLE DROP COLUMN Hiroshi Inoue
- Re: AW: [HACKERS] ALTER TABLE DROP COLUMN Hiroshi Inoue
- Re: AW: [HACKERS] ALTER TABLE DROP COLUMN Hannu Krosing
- RE: AW: [HACKERS] ALTER TABLE DROP COLUMN Don Baccus
