From: | "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk> |
---|---|
To: | Chris Bitmead <chris(at)bitmead(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [HACKERS] Inheritance, referential integrity and other constraints |
Date: | 2000-01-25 08:06:34 |
Message-ID: | 200001250806.IAA03764@linda.lfix.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Chris Bitmead wrote:
>As long as you're working on this area you could fix the problem where
>if you do ALTER table* ADD COLUMN ... pg_dump no longer works because
>the column orders have changed in different inherited tables.
It seems that this might be quite a problem; I would not like to have
to do a physical insert into every row in a huge table. Would it be
feasible to add a column order attribute to pg_attribute for tables
altered in this way? A null entry in that would indicate the table was unaltered from its creation.
Perhaps this could be combined with the idea of column hiding: a zero
column number would mean it was hidden.
--
Oliver Elphick Oliver(dot)Elphick(at)lfix(dot)co(dot)uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP key from public servers; key ID 32B8FAA1
========================================
"My little children, let us not love in word, neither
in tongue; but in deed and in truth."
I John 3:18
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2000-01-25 08:20:20 | Re: [HACKERS] DISTINCT ON: speak now or forever hold your peace |
Previous Message | Philip Warner | 2000-01-25 07:54:59 | Re: [HACKERS] DISTINCT ON: speak now or forever hold your peace |