Fix for possible referential integrity violation when a qualified ON INSERT
authorJan Wieck <JanWieck@Yahoo.com>
Fri, 31 Oct 2003 03:57:42 +0000 (03:57 +0000)
committerJan Wieck <JanWieck@Yahoo.com>
Fri, 31 Oct 2003 03:57:42 +0000 (03:57 +0000)
commitd1c496e9d58f984731f9385e001d8259cdecfd8c
tree06867770e3a6faada4da7130bafb0fa20ccf5dc6
parent9e692f230737cacfda83efc7a7bda522501c2bf9
Fix for possible referential integrity violation when a qualified ON INSERT
rule split the query into one INSERT and one UPDATE where the UPDATE
then hit's the just created row without modifying the key fields again.
In this special case, the new key slipped in totally unchecked.

Jan
src/backend/utils/adt/ri_triggers.c
src/test/regress/expected/foreign_key.out
src/test/regress/sql/foreign_key.sql