I have a parent table with 2 children tables. The 2 children would be siblings with no real relationship to each other but through the parent.
Based upon what I've read in the docs, I feel like the children should have a manytoone to the parent. But if I want to do a cascadeCreate() that writes a new record to all of these tables at once, it seems I have to reverse that relationship and do a onetoomany from the parent to the children. What would be best practices here? I don't necessarily feel like the cascadeCreate() saves me so much effort that if a m2o is favored over a o2m in this scenario I couldn't just do the manual creates on each table. Thanks, -- Matt Williams "It's the question that drives us." --~--~---------~--~----~------------~-------~--~----~ Before posting questions to the group please read: http://groups.google.com/group/transfer-dev/web/how-to-ask-support-questions-on-transfer You received this message because you are subscribed to the Google Groups "transfer-dev" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/transfer-dev?hl=en -~----------~----~----~----~------~----~------~--~---
