title: angularjs $resource and one-to-many relationship
body: <p>what is the right way to use ngResource for a complex data model?
  There are countless one-table examples out there, but little to nothing covering 1:n and m:n relationships.</p>
  
  <p>Assuming a simple 'parent' 1->n 'child' relationship, and the entry point is always through parent: is it necessary to create a $resource for parent and child, and call save() on the child for each time a new related child is created, passing the parent_id? Or did my way of thinking not arrive in the Angular world yet, and I should try to save() the parent only having ngResource taking care of the rest? </p>