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
Showing
- src/backend/utils/adt/ri_triggers.c 4 additions, 2 deletionssrc/backend/utils/adt/ri_triggers.c
- src/test/regress/expected/foreign_key.out 59 additions, 0 deletionssrc/test/regress/expected/foreign_key.out
- src/test/regress/sql/foreign_key.sql 58 additions, 0 deletionssrc/test/regress/sql/foreign_key.sql
Loading
Please register or sign in to comment