Open jeroen11dijk opened 3 hours ago
Hmm...this definitely is a bug, somewhere in ash_postgres
when constructing a changeset for destroy, where we are not properly configuring the foreign key names I imagine. Did you perhaps edit the name of the foreign key constraint manually? matching_table_entry_timeslot_id_fkey
looks like the default we'd assume, just want to double check.
Describe the bug had a chat about the error here: https://discord.com/channels/711271361523351632/1069610909296766998/1308825724760752270
So we have a matching table with these relations
And then timeslot has the following:
And lastly entry:
But now when I try to delete a matching table which has a timeslot which has an entry I get the following error:
Yet I expect that like I one had before I get an error that says "would leave records behind" and is also an actual error. Both restrict and nothing give me the same result.
Feel free to ask more questions on discord.
To Reproduce See above
Expected behavior An actual error with the message "would leave records behind" which I have seen before.