Message-ID: <45237D6E.1030601@logix-tt.com>
Date: Wed, 04 Oct 2006 11:22:54 +0200
From: Markus Schaber <schabi@logix-tt.com>
Organization: Logical Tracking and Tracing International AG, Switzerland
User-Agent: Thunderbird 1.5.0.5 (X11/20060812)
MIME-Version: 1.0
To: pgsql-sql@postgresql.org
Subject: Re: i have  table
References: <A70AE049E81A6A40879D5DC0AC8C38C9073DCD8F@venus.infics.com>
In-Reply-To: <A70AE049E81A6A40879D5DC0AC8C38C9073DCD8F@venus.infics.com>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

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 fiel=
d
> it is coming last field =E2=80=A6

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=E2=80=A6

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


--=20
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf.     | Software Development GIS

Fight against software patents in Europe! www.ffii.org
www.nosoftwarepatents.org