RE: ALTER TABLE DROP COLUMN
От | Hiroshi Inoue |
---|---|
Тема | RE: ALTER TABLE DROP COLUMN |
Дата | |
Msg-id | 001301bfd500$a58d9960$2801007e@tpf.co.jp обсуждение исходный текст |
Ответ на | Re: 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: > > create table t1 (i1 int4); > > create table t2 (i2 int4) inherits t1; > > create table t3 (i3 int4) inherits t2; > > alter table t1 add column i4 int4; > > > For each table,the list of (column, logical number, physical number) > > would be as follows. > > > t1 (i1, 1, 1) (i4, 2, 2) > > t2 (i1, 1, 1) (i4, 2, 3) (i2, 3, 2) > > t3 (i1, 1, 1) (i4, 2, 4) (i2, 3, 2) (i3, 4, 3) > > > At this point the compilation of 'select * from t1(*?)' would mean > > select (physical #1),(physical #2) from t1 + > > select (physical #1),(physical #3) from t2 + > > select (physical #1),(physical #4) from t3 > > > Note that physical # aren't common for column i4. > > That's no different from the current situation: Yes your proposal has no problem currently. I'm only anxious about oo feature. Recently there has been a discussion around oo and we would be able to expect the progress in the near future. If oo people never mind, your proposal would be OK. Regards. Hiroshi Inoue Inoue@tpf.co.jp
В списке pgsql-hackers по дате отправления: