[Rails] Is a controller called "home" sort of a standard or best practice?

Is it pretty much a standard, best practice or just a good idea to create a controller called "home" and put, say, my web sites home page ('index.html.erb') there?? -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group,

Re: [Rails] Newbie: I just want to exclude two attributes when I call update_attributes

And in the Create method as well. This FEELS wrong, but it works. On Saturday, January 19, 2013 10:44:21 AM UTC-5, Don Schenck wrote: > > Colin -- > > I ended up using > > > .slice(:field1, :field2, :field4) > > > in my update. Works fine. > > -- Don > &

Re: [Rails] Newbie: I just want to exclude two attributes when I call update_attributes

Colin -- I ended up using .slice(:field1, :field2, :field4) in my update. Works fine. -- Don On Saturday, January 19, 2013 4:17:26 AM UTC-5, Colin Law wrote: > > On 18 January 2013 21:44, Don Schenck > > wrote: > > I have two virtual attributes in my mode

[Rails] Newbie: I just want to exclude two attributes when I call update_attributes

I have two virtual attributes in my model. Let's call them "hours_worked" and "minutes_worked". I use them to calculate "work_time", which is an integer I store -- it's the total minutes worked (e.g. 3.5 hours is 210). I want :hours_worked and :minutes_worked to NEVER appear in the database. B