On 13 August 2013 17:46, Scott Ribe <[email protected]> wrote: > On Aug 13, 2013, at 12:43 AM, Valentin Kotelnitski <[email protected]> > 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.
But before doing anything else work through railstutorial.org or similar, as I have suggested several times I think. Otherwise in the future you will look back at your requests for help here and wish to die from embarrassment. Colin -- 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 [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/CAL%3D0gLs5xWcCgs6Qph%2B4euHH3oES8iCMeTJj4d5r-nP%2BunHtUQ%40mail.gmail.com. For more options, visit https://groups.google.com/groups/opt_out.
