Ruby on Rails Tuesday, August 13, 2013

On Aug 13, 2013, at 12:43 AM, Valentin Kotelnitski <lists@ruby-forum.com> wrote:

> As I see now there is no way of not regenerating model.

No, there is absolutely no need to re-generate your model. *That* is what people are telling you.

> Earlier I just
> hoped it could be possible to add a piece of hand-written code to my
> model to access newly added column in the last database migration.

You can do exactly that. It is also likely that you don't even need to.

- Simple access to the column comes for free. You don't need to do anything.

- Of course if you need to use that column within some larger function of the model, you will edit the model to add that. But you will *not* need to edit it to add simple accessors to get/set the column, those come for free and you will just use them.

--
Scott Ribe
scott_ribe@elevated-dev.com
http://www.elevated-dev.com/
(303) 722-0567 voice




--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-talk+unsubscribe@googlegroups.com.
To post to this group, send email to rubyonrails-talk@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/F00E8C9B-DBDB-44A2-9EFD-BE70B39E8DE5%40elevated-dev.com?hl=en-US.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment