Fix for possible referential integrity violation when a qualified ON INSERT
authorJan Wieck <[email protected]>
Fri, 31 Oct 2003 03:57:42 +0000 (03:57 +0000)
committerJan Wieck <[email protected]>
Fri, 31 Oct 2003 03:57:42 +0000 (03:57 +0000)
commit345fdf1d057bc3bf35e6cc7ce22b2dbc4f5f011a
tree7cf0fa580f23face18e5951e92198a4d05f02c89
parent78856b8863cd2cd58849737e8684649906fdc844
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