does the column order within a table matter? i had to
delete a column when making a foreign key b/c int4[]
didn't allow the reference. i deleted int4[] and
recreated the table with int4 and everything was fine
- except my column order within my table was
different. does this make a difference beyond losing
some visual and organizational appeal?

can pgadmin3 rearrange the order of the columns?

tia...



__________________________________
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

operationsengineer1@yahoo.com wrote:
> does the column order within a table matter? i had to delete a
> column when making a foreign key b/c int4[] didn't allow the
> reference. i deleted int4[] and recreated the table with int4 and
> everything was fine - except my column order within my table was
> different. does this make a difference beyond losing some visual and
> organizational appeal?
>
> can pgadmin3 rearrange the order of the columns?
>
> tia...
>
It shouldn't matter. The only place it might matter is if you are doing a
select * from table
And the code that is reading the results cares about the column order.



--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 E-Mail: ler@lerctr.org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749



---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?

http://www.postgresql.org/docs/faq