<p>MySQL has commands for disabling FK checks. Not sure if we should go that route or not, but I'm going to have to side with <a href="https://github.com/gbarr" class="user-mention">@gbarr</a> on this being a critical support issue, previous behavior be damned. We can't just say that we don't support cascade deletes when we have a cascade_delete flag in the relationship.</p>
<p>Sure, the exception is documented, and yes, it's been in there forever. But causing an exception for a fairly common use case is still a bug, especially when there isn't any way around it. Let's provide some answers instead of constantly shooting down his suggestions.</p>
<p>I'm in favor of creating a cascade_delete => -1 behavior. It doesn't create a dual property complexity problem, passes TRUE/FALSE tests (on the edge case of relationship introspection), and it's mnemonic. (After = 1, Before = -1)</p>
<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br>Reply to this email directly or <a href='https://github.com/dbsrgits/dbix-class/pull/27#issuecomment-18457621'>view it on GitHub</a>.<img src='https://github.com/notifications/beacon/4W3BWTo7EIi_7vx28Xzl_mJnCwjxj52C33_Ervpy2ogo-MvpszQvTwkKiTOIEY0G.gif' height='1' width='1'></p>