| From: | Colin Beckingham <colbec(at)start(dot)ca> | 
|---|---|
| To: | pgadmin-support(at)postgresql(dot)org | 
| Subject: | 1.15 DD - order of columns | 
| Date: | 2012-04-21 11:32:43 | 
| Message-ID: | 4F929ADB.5040700@start.ca | 
| Views: | Whole Thread | Raw Message | Download mbox | Resend email | 
| Thread: | |
| Lists: | pgadmin-support | 
Another issue with creating SQL from the DD is that unpredictably the 
order of columns will change. Say you have authid, authname in your 
original table, your copy might be defined as or authid, authname or 
authname, authid in the copy.
Order of columns is important in Postgresql since it can't easily be 
changed after table is created without delete and add back in a specific 
order.
It appears to be important with respect to import of data from CSV, for 
example, where even if the header defines columns in a specific order, 
the import does not pick that up.
Workaround is of course to open up the csv in a SS, rearrange the cols 
to suit, and export back to CSV, or simply drop and recreate the table 
using the SQL from the original definition if you have that option.
-- 
---
Colin Beckingham
613-454-5369
http://www.it4gh.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Colin Beckingham | 2012-04-21 15:06:07 | 1.15 DD - serial copied as integer | 
| Previous Message | Colin Beckingham | 2012-04-21 10:11:14 | Re: 1.15 Database Designer and character varying length option |