Evan, Don't overdo your requirements. Take your requirements lightly.
>From what I can see in your example, Leader plays a larger role in your domain, so it has priority over the Conversation. I would model Leader having zero or more (0..*) Conversations, Conversation having 1 Leader. A simple one to many relationship between those domain objects. As from what I can tell, your are trying to create both at the same time in the view, thus sending both objects over to the controller. While creating a Conversation, you could give the user the opportunity to create a Leader, if its currently not available, or he wants to get a new one. You could use AJAX to access the create action in the leader controller having it available prior to saving the Conversation. Check out this resource by Ryan Bates. http://railscasts.com/episodes/57-create-model-through-text-field Regards, Rodrigo Dellacqua IBM - IGF Project Manager "Communication is the key" On Wed, Dec 30, 2009 at 8:50 PM, Evan Chaney <[email protected]> wrote: > > That way you can't save a conversation without assigning it a leader, > > but the leader doesn't have to be saved yet. > > Well, that’s where I’m at right now. I’d like to be in a situation where > Conversation validates that it has a Leader and Leader validates it has a > Conversation before either is saved. > > -- > > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<rubyonrails-talk%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/rubyonrails-talk?hl=en. > > > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
