From: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | "Gregory Stark" <stark(at)enterprisedb(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: why it doesn't work? referential integrity |
Date: | 2007-08-11 13:44:05 |
Message-ID: | 162867790708110644p6ea2b9f6wb60da5294f697988@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
2007/8/11, Gregory Stark <stark(at)enterprisedb(dot)com>:
>
> "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)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
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2007-08-11 14:35:20 | Re: why it doesn't work? referential integrity |
Previous Message | Janning Vygen | 2007-08-11 13:00:17 | Re: why it doesn't work? referential integrity |