From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
---|---|
To: | Andreas Pflug <pgadmin(at)pse-consulting(dot)de> |
Cc: | pg(at)fastcrypt(dot)com, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Neil Conway <neilc(at)samurai(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: logical column position |
Date: | 2003-11-20 01:21:45 |
Message-ID: | 3FBC1729.7010400@familyhealth.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Why should ALTER COLUMN change the column number, i.e. position?
Because it creates a NEW column.
>> It may be that programmers should not rely on this, but it happens,
>> and in very
>> large projects. If we can avoid unexpected side-affects like moving the
>> columns position, then I think we should.
>>
>>
> This is *expected* if behaviour if you delete and add columns; is there
> any DB system out there that allows to reshuffle the column ordering?
MySQL
Chris
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2003-11-20 03:50:41 | Re: question about fixes in v7.4... |
Previous Message | Christopher Kings-Lynne | 2003-11-20 01:17:29 | Re: Is there going to be a port to Solaris 9 x86 in the |