Re: updating data but the constraint is set "immediate"
От | Rudy Koento |
---|---|
Тема | Re: updating data but the constraint is set "immediate" |
Дата | |
Msg-id | 20030702030310.6593.qmail@web41609.mail.yahoo.com обсуждение исходный текст |
Ответ на | Re: updating data but the constraint is set "immediate" (Bruno Wolff III <bruno@wolff.to>) |
Список | pgsql-general |
--- Bruno Wolff III <bruno@wolff.to> wrote: > On Tue, Jul 01, 2003 at 02:35:48 -0700, > Rudy Koento <rudy_koento@yahoo.com> wrote: > > Hi, > > > > I've realised that my tables' constraint was set > to > > IMMEDIATE. So, when I update one table, there's > error > > because of referential integrity. Reading the > docs, I > > read that SET CONSTRAINTS has no effect on > IMMEDIATE > > (and I've confirmed that by trying it out). > > > > Is there anyway I can circumvent this? I > remembered I > > can delete using pgAdminII. However, I don't have > a > > windows box now, and therefore I can't use > pgAdminII. > > You can use alter table to drop the constraint and > then to add the corrected > constraint. I am not sure if this was available > prior to 7.3. I solved it by using pgAdminII remotely through ssh port forwarding. I'm curious though, as to why does pgAdminII is able to defer the constraints whereas using command line cannot... __________________________________ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com
В списке pgsql-general по дате отправления: