Re: why it doesn't work? referential integrity

"Pavel Stehule" <pavel.stehule@gmail.com> writes:

> 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

There's no delete from users in evidence here.

Check how your constraints are actually defined, it doesn't look like they're
defined they way you claimed they are


--
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com