You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
lets say there is an orphan model called Exam and each Exam has many ExamSections. If there is an orphan ExamTemp it should be able to have_manyExamSectionTemps and there adoption should be handled automatically by calling adopt on the parent.
Currently this is possible to do manually, buy setting the association with the child record, and setting up a transaction to handle all of the adoptions. I'm thinking about streamlining it a bit more. This would mean
calling Orphanage:Init has an option to specify a child association
calling adopt automatically tries to bring in children as well
The text was updated successfully, but these errors were encountered:
lets say there is an orphan model called
Exam
and eachExam
has manyExamSection
s. If there is an orphanExamTemp
it should be able tohave_many
ExamSectionTemp
s and there adoption should be handled automatically by callingadopt
on the parent.Currently this is possible to do manually, buy setting the association with the child record, and setting up a transaction to handle all of the adoptions. I'm thinking about streamlining it a bit more. This would mean
Orphanage:Init
has an option to specify a child associationadopt
automatically tries to bring in children as wellThe text was updated successfully, but these errors were encountered: