From: Erik Jones <erik@myemma.com>
To: Markus Schaber <schabi@logix-tt.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: i have table
Date: Wed, 04 Oct 2006 09:23:30 -0500
Message-ID: <4523C3E2.4010300@myemma.com> (raw)
In-Reply-To: <45237D6E.1030601@logix-tt.com>
References: <A70AE049E81A6A40879D5DC0AC8C38C9073DCD8F@venus.infics.com>
<45237D6E.1030601@logix-tt.com>
There is one non-SQL related reason that I like to be able to order
columns, at least the way they are displayed whenever the table is
described: human comprehension. For example, I like to group all keys
in a table before data, that includes primary as well as foreign keys.
So, say I'm building on to an existing application and I need to do an
ALTER TABLE on an existing table to add a foreign key to an existing
table. I'd like that key to be listed with the other keys, but
presently that's not possible in a simple way and, to be honest, I
usually just go without as the process you've described below is too
prone to user (human) error when dealing with live, sensitive data for
me to want to mess with it.
Markus Schaber wrote:
> Hi, Penchalaiah,
>
> Penchalaiah P. wrote:
>
>
>> now I want to add one more field in this table.. but that field has to
>> come next to cda_no.. I mean as a 3^rd field.. If I am adding that field
>> it is coming last field …
>>
>
> In SQL, field order in the table is not given by design.
>
> A "SELECT * FROM table" might even give you the columns alphabetically
> ordered, or in a different random order each time in a different server
> implementation.
>
> If you need the colums in a specific order, use "SELECT foo, bar, baz
> FROM table" or create a View.
>
> All relevant SQL constructs (SELECT, INSERT, UPDATE, COPY, etc.) let you
> specify the columns explicitly to guarantee a given order.
>
>
>> may I know how it is possible to that table…
>>
>
> If you _really_ want to do that despite what I wrote above, you have
> several possibilities:
>
> - COPY the table to some file, drop the table, recreate the table with
> the desired new column order, and then COPY the table back using an
> explicitly specified, correct row order.
>
> - use CREATE TABLE ... AS SELECT to select the data into a new table,
> drop the old table, rename the new one to the old one.
>
> In both cases, you've to recreate all missing indices, foreing key
> constraints etc.
>
>
> HTH,
> Markus
>
>
>
--
erik jones <erik@myemma.com>
software development
emma(r)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: erik@myemma.com, schabi@logix-tt.com
Subject: Re: i have table
In-Reply-To: <4523C3E2.4010300@myemma.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox