From: | Melanie Renee Nelson <mnelson(at)scripps(dot)edu> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Subject: | dropping a column from a table |
Date: | 1998-10-05 17:19:16 |
Message-ID: | Pine.SGI.3.95.981005101229.10528C-100000@bianca |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I have been following the discussion about dropping a column with
interest, because I ran into this problem just last week. The table I
wanted to alter is very central in my database, and therefore has a lot of
foreign key triggers defined on it. Am I correct that the method suggested
in the FAQ would cause any triggers defined on the table to be altered to
be lost (due to the DROP TABLE portion)? I was afraid this would be the
case, and didn't want to have to redefine all those triggers, so I didn't
use this method. My database is still young, and it doesn't have any user
defined rules or views or any of the other thing pg_dump can't handle, so
I just dumped my database, altered the resulting output file to make the
changes I wanted in my table, and then recreated my database.
Are there any hidden dangers in this method (besides the obvious ones due
to the limitations of pg_dump as spelled out in the man pages)?
Thanks
--Melanie
************************************************************************
Melanie Nelson mnelson(at)scripps(dot)edu
Graduate Student http://www.scripps.edu/~mnelson
The Scripps Research Institute (619) 784-9879
************************************************************************
From | Date | Subject | |
---|---|---|---|
Next Message | Antonio Garcia Mari | 1998-10-05 18:10:22 | Bug? Inserting with not null |
Previous Message | Sangeeta Rao | 1998-10-05 17:03:41 | Default 'timestamp' value on HP-UX running Postgresql6.3.2 |