Re: why it doesn't work? referential integrity
От | Pavel Stehule |
---|---|
Тема | Re: why it doesn't work? referential integrity |
Дата | |
Msg-id | 162867790708110644p6ea2b9f6wb60da5294f697988@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: why it doesn't work? referential integrity (Gregory Stark <stark@enterprisedb.com>) |
Ответы |
Re: why it doesn't work? referential integrity
|
Список | pgsql-general |
2007/8/11, Gregory Stark <stark@enterprisedb.com>: > > "Pavel Stehule" <pavel.stehule@gmail.com> writes: > > > checked_by INT REFERENCES users (id) ON UPDATE CASCADE ON DELETE SET NULL, > > > CONTEXT: SQL statement "UPDATE ONLY "public"."tasks" SET "worker" = > > NULL WHERE $1 OPERATOR(pg_catalog.=) "worker"" > > This says you mistyped the constraint above to refer to tasks(worker) instead > of users(id). Did you? > > -- Im sorry. I don't understand. It's look like wrong evaluation order: 1. delete from users 2. update tab set col = NULL insead 1. update ... -- remove references 2. delete from users ... Pavel Stehule > Gregory Stark > EnterpriseDB http://www.enterprisedb.com > >
В списке pgsql-general по дате отправления: