At 22:43 13/09/00 -0400, Tom Lane wrote:
>
>> Am I correct that someone was working on allowing a column order to be
>> specified in COPY commands? If so, this would fix the problem, I think.
>
>No, that is a kluge that would allow pg_dump to work around ALTER
>TABLE's fundamental inadequacy. It's not a fix unless you think it's OK
>to expect every application forevermore to take special care with column
>orders.
>
I suppose from an application programming point of view, I am used to
having to specify column order in my 'select' statements (ie. I don't tend
to let 'select * from...' into production code, and usually consider it bad
form to do so), so I thought the issue was confined to COPY & pg_dump. And
in the case of pg_dump, I would just explicitly set the column order when
they are dumped/restored.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \| | --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
