Rasmus Rasmussen wrote: > Thanks for info, appreciated! > > I suspect it is weird to do a PeriodController just to keep the > Period-code somewhere. So, where would you put create-code for the > models that does not have own controllers? Actually it wouldn't weird at all.
Although I don't know your whole design, I would envision Period as a nested resource of Calendar. map.resources :calendars, :has_many => :periods This would give you routes such as: POST: calendars/1/periods GET: calendars/1/periods/1 PUT: calendars/1/periods/3 DELETE: calendars/1/periods/4 -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
