On 21 June 2011 14:31, mukesh singh <mukesh23.si...@gmail.com> wrote: > Thanks for your reply
Please don't top post, it makes it difficult to follow the thread. Insert your reply at appropriate points in previous message. Thanks. > I thought class_eval method would permanently add assignee_name method to > Assignee instance object and i can access from other action too. I think it will, but only when you execute the class_eval code. Permanent means of course until you restart the server or reload the Assignee class. Since in development mode classes are reloaded at each action request it will not hold from one request to the next, if that is what you are trying to do. Even in production this is a bad thing to do as you never know when a server might get restarted and loose the data. Not to mention the fact that once in production successive actions are not necessarily even run by the same computer. If you want retain information from one action to the next then put it in the session or in the database, or in a hidden field in the intervening view. I think Chirag Singhal's suggestion is better though unless there is some reason you cannot use it. Colin > > On Tue, Jun 21, 2011 at 5:20 PM, Chirag Singhal <chirag.sing...@gmail.com> > wrote: >> >> Curious why you would want to define the method that way, are you >> overriding the method assignee_name which is already defined in the Assignee >> class? >> If not, then why not define it directly in the model like this: >> def assignee_name(assigned_by) >> self["assigned_by"] >> end >> Controller method will be >> def do_assignee_cleaning >> Assignee.assignee_name(params[:assignee_by]) >> redirect_to >> assignee_cleaning_project_assignees_path(params[:project_id]) >> end >> >> -- > > >> >> You received this message because you are subscribed to the Google Groups >> "Ruby on Rails: Talk" group. >> To view this discussion on the web visit >> https://groups.google.com/d/msg/rubyonrails-talk/-/aVbAUtgf5QQJ. >> To post to this group, send email to rubyonrails-talk@googlegroups.com. >> To unsubscribe from this group, send email to >> rubyonrails-talk+unsubscr...@googlegroups.com. >> For more options, visit this group at >> http://groups.google.com/group/rubyonrails-talk?hl=en. > > > > -- > Regards > Mukesh Paras Singh > > -- > 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 rubyonrails-talk@googlegroups.com. > To unsubscribe from this group, send email to > rubyonrails-talk+unsubscr...@googlegroups.com. > 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 rubyonrails-talk@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-talk+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
