on 2017 Dec 11 8:13 AM
Hello guys,
I have a question regarding the "CHECK ON COMMIT" foreign key option during a table creation. When should I set this on/off?
I ask that because we are facing some weird bug in our system.
In a specific screen we execute a "UPDATE ... WHERE id = ?", where id has a foreign key to another table. However, this statement fails in some situations with a foreign key violation over "id" column (no ids are updated by this statement).
The weird part is that all the FK violations happens when this statement is executed along with a synchronism.
I was thinking that the "update" fails because the statement is executed after the referenced id is removed from database, by the synchronism.
Could you enlighten me with some insights about what could be happening?
Request clarification before answering.
User | Count |
---|---|
52 | |
10 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.