Back
Bug in relational table
I potential found a bug or is there something I am missing?
I created 2 tables. User and Coins User has a one to one relation to Coins When attempting to create a entry in User with the relational object for Coins while the creation of the User entry throws an error the Coin object is still created.
I expect if the User row cant be created, that also the Coin row wont be created.
TL;DR
Developers found a bug in the relational table setup where creating a User entry with a relational Coins object throws an error, but still creates the Coin row. The expected behavior was for the Coin row not to be created if the User row creation failed.
Solution:
To ensure that the Coin row is not created if the User row creation fails, the developers need to implement a transaction system where both operations are either committed or rolled back together.