User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.100 Safari/537.36
Performing an INSERT seems to violate the foreign key constraints that refer the same table, where the referred key is also the same inserted key. This is inconsistent with the behaviour of disabling the foreign key, inserting the data, and eventually re-enabling the foreign key constraint. In this latter case the INSERT statements succeed.
AFAIK any foreign key constraint should be checked after the update has taken place, so that the former statement should be allowed.
Steps to Reproduce:
1. See attached repro
The INSERT statement is rejected due to the foreign key being violated
The INSERT statement should be allowed
Created attachment 516 [details]
Changeset 73b379ba7970, made by Martin van Dinther <firstname.lastname@example.org> in the MonetDB repo, refers to this bug.
For complete details, see http://dev.monetdb.org/hg/MonetDB?cmd=changeset;node=73b379ba7970
Add test for bug 6131
*** Bug 6132 has been marked as a duplicate of this bug. ***