-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Cloning complex model relationships #175
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
@fabianallendorf This might be resolved now but I'll setup a test to replicate. Giving the current design House 1 name (My House) House 2 name (My House)
| Clone |
(1st room) / \ (2nd room) (1st room) / \ (2nd room)
Room 1 Room 2 =-----> Room 3 Room 4
(chair) / \ (chair) (chair) / \ (chair)
Chair 1 Chair 2 Chair 3 Chair 4 It would be helpful to fully understand your use case would you like to share the same |
@fabianallendorf Let me know if this is still a blocker ? |
@fabianallendorf closing this issue for now let me know if this is still a requirement using the latest version. |
Is your feature request related to a problem? Please describe.
I have a complex database structure. Its better to be explained using an example:
Lets say I want to clone a
House
object which has a fewRoom
andFurniture
objects. The problem arises that, when it clones aFurniture
object, it will update the foreign key tohouse
but notroom
. Or when I cloneRoom
it will update theroom
foreign key but not thehouse
foreign key.This way I can imagine to end up in a state where cloned Furniture objects exist twice with either a reference to
Room
orHouse
missing.Describe the solution you'd like
I would want to have a mechanism were I can tell the
Furniture
during cloning that it has to update both foreign keys accordingly.Describe alternatives you've considered
Passing a map of old and new instances down the foreign key relationship path which lower level objects can access to update every foreign key.
The text was updated successfully, but these errors were encountered: