RE: AW: ALTER TABLE DROP COLUMN
От | Hiroshi Inoue |
---|---|
Тема | RE: AW: ALTER TABLE DROP COLUMN |
Дата | |
Msg-id | EKEJJICOHDIEMGPNIFIJGEOJCIAA.Inoue@tpf.co.jp обсуждение исходный текст |
Ответ на | Re: AW: ALTER TABLE DROP COLUMN (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
> -----Original Message----- > From: Tom Lane [mailto:tgl@sss.pgh.pa.us] > > "Hiroshi Inoue" <Inoue@tpf.co.jp> 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? > Yes,the implementation would be almost same. I've been busy for some time and wasn't able to follow this thread. Don't people love 2x DROP COLUMN ? I don't object to 2x DROP COLUMN if it could be implemented properly though I don't want to implement it myself. However I would strongly object to 2x ADD COLUMN if such implementations are proposed. Regards. Hiroshi Inoue
В списке pgsql-hackers по дате отправления: