Skip site navigation (1)
Skip section navigation (2)
Hello,
It is often convenient to have columns of a table in certain order (as shown by psql or most GUI database explorers, it also affects INSERT's without columns specified behavior) so as to most significant columns to come first, semantically close columns to be grouped etc, while the columns might be added to the table in different order during development process. So, the question is - is it an acceptable way to play with pg_attribute's attnum and set it to needed value or recreate the table is the only way? On the related note - should the columns necessarily be numbered from 1 up with the step of 1?
Thanks,
Viatcheslav
Peripheral Links
Header And Logo
|
Site Navigation
Column order
- From: "Vyacheslav Kalinin" <vka(at)mgcp(dot)com>
- To: PGSQL <pgsql-general(at)postgresql(dot)org>
- Subject: Column order
- Date: Thu, 24 Apr 2008 05:33:21 +0400
- Message-id: <9b1af80e0804231833s655296a5m3c7f8e3f4d5fd8eb(at)mail(dot)gmail(dot)com>
Hello,
It is often convenient to have columns of a table in certain order (as shown by psql or most GUI database explorers, it also affects INSERT's without columns specified behavior) so as to most significant columns to come first, semantically close columns to be grouped etc, while the columns might be added to the table in different order during development process. So, the question is - is it an acceptable way to play with pg_attribute's attnum and set it to needed value or recreate the table is the only way? On the related note - should the columns necessarily be numbered from 1 up with the step of 1?
Thanks,
Viatcheslav
- Follow-Ups:
- Re: Column order
- From: Robert Treat
- Re: Column order
- Prev by Date: Re: Need to update all my 60 million rows at once without transactional integrity
- Next by Date: Re: Column order
- Previous by thread: Table with differerent Data Types
- Next by thread: Re: Column order
- Indexes: