| From: | Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> |
|---|---|
| To: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLE DROP COLUMN |
| Date: | 2000-06-13 00:16:24 |
| Message-ID: | 39457D58.F342701A@nimrod.itg.telecom.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hiroshi Inoue wrote:
> I don't understand inheritance well. In the near future wouldn't the
> implementation require e.g. attid which is common to all children
> of a parent and is never changed ? If so,we would need the third
> attid field which is irrevalent to physical/logical position. If not,
> physical column number would be sufficient .
We only need something like a unique attid of course if we support
column renaming in child tables. Otherwise the attname is sufficient to
match up child-parent columns.
If/when we support renaming, probably a parent_column_oid in
pg_attribute might be one way to go.
Your idea seems fine Tom.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | valter m | 2000-06-13 00:32:06 | how an app can know when a table is altered ? |
| Previous Message | Bruce Momjian | 2000-06-13 00:15:01 | Re: Proposal for fixing intra-query memory leaks |