You shouldn't rely on ID's to be in any particular order, there are a lot of things that can happen. You could assign another DB column to represent the ordering somehow If you want to do it though, just save the people as you create them, since that is when the ID's will get assigned: new_person = @team.persons. Build new_person.
Name = p. Name new_person. Save If you're worried about database consistency, wrap the for loop and the team.
Save in a transaction, so they all get rolled back if one fails.
You shouldn't rely on ID's to be in any particular order, there are a lot of things that can happen. You could assign another DB column to represent the ordering somehow. If you want to do it though, just save the people as you create them, since that is when the ID's will get assigned: new_person = @team.persons.
Build new_person. Name = p. Name new_person.
Save If you're worried about database consistency, wrap the for loop and the @team. Save in a transaction, so they all get rolled back if one fails.
I setup the association between the two before running any migrations, so I don't see why this has not been setup correctly.
I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.