-
Notifications
You must be signed in to change notification settings - Fork 77
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Undefined index notice on nested call #97
Comments
Both workarounds seem to work and pass the (updated) tests. |
Not unsetting the original data could be a problem on this line: @xhs345 do you know why there is no |
Also refactores all original data related actions into reusable methods.
@ravage84 Nope, don't know why |
Easy, already documented as #82 |
Closing this since your fix has been merged |
My situation:
Rack
hasManyRackUnit
(fully pedendent)RackUnit
belongsToReservation
(optionally)Deleting a
Rack
, deletes all itsRackUnit
.If one of those
RackUnit
belongTo aReservation
, thatReservation
will be deleted, too.If a
Reservation
gets deleted, another behavior will unset (means updated, not deleted) all reservedRackUnit
.This leads to a nested call stack, which in turn leads to a
Undefined index: RackUnit
notice.The simplified call stack is:
I see two workarounds an one solution.
The text was updated successfully, but these errors were encountered: