From: | Ian Harding <harding(dot)ian(at)gmail(dot)com> |
---|---|
To: | Scott Ribe <scott_ribe(at)killerbytes(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Reordering columns in a table |
Date: | 2006-01-07 03:34:19 |
Message-ID: | 725602300601061934i61219371vb7dddb0be1ea868@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-general |
As I recall, the MS SQL Server draggy droppy diagrammer tool made it
seem trivial to rearrange columns did the same thing. It just
generated SQL statements to:
Begin transaction
select data in new order into a new table
drop dependent objects
drop old table
rename new table
re-create dependent objects
end transaction
It seemed kinda squirrelly to me, but it worked most of the time since
MSSQL Server had a good dependency tracking thingie. However, I would
not really call it a feature of the DBMS. I would call it a bolted on
utility.
On 1/6/06, Scott Ribe <scott_ribe(at)killerbytes(dot)com> wrote:
> > I would assume
> > that all dependent database objects are also dropped when you drop the
> > table, so you'd have to recreate all of your foreign keys (both
> > directions) and triggers etc.?
>
> Basically. I try to keep my DDL scripts organized in a way that makes this
> easy. Of course an automated tool could do this as well. For instance I used
> to use the products from Embarcadero to maintain Sybase databases, and their
> design tool would create all the DDL needed to update a live database to
> match the current design. Of course, one experience with a bug and I learned
> to have it show me the script and read it carefully before proceeding ;-)
> (Hey, I'm not stupid, it was just a development db that I hosed!)
>
>
> --
> Scott Ribe
> scott_ribe(at)killerbytes(dot)com
> http://www.killerbytes.com/
> (303) 665-7007 voice
>
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 2: Don't 'kill -9' the postmaster
>
From | Date | Subject | |
---|---|---|---|
Next Message | John Supplee | 2006-01-07 11:35:03 | Re: BUG #2144: Domain NOT NULL constraints ignored in rules |
Previous Message | Vic | 2006-01-06 22:13:07 | BUG #2155: problem with UNICODE and KOI8 |
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Fuhr | 2006-01-07 04:05:16 | Re: plpgsql question |
Previous Message | Mike | 2006-01-06 23:38:44 | Re: How to search? |