Thanks for an additional response, Marnen. > Not quite. You do not need to change your model at all -- it will > figure out that the extra DB fields are there.
Interesting ... may I conclude that a Rails app, at start-up, consults the database the app points to and determines the fields and their types of every table? > script/generate model and controller will not help. script/generate > scaffold might, but you're better off modifying your views manually. I anticipated this response and decided to forge ahead and make changes manually. I ran into a problem after I added some erb comments to four CRUD modules in app\views\expenses. I'm working on that right now. > > The > > question about whether I use git or my external hard drive are > > tangential to the issue I'm dealing with. Likewise, whether I use > > formal or ad hoc testing > > Not really. ... I'm not disputing the value of Agile Programming. But clients wouldn't tolerate me taking time to employ "best practices of to last century" and my current "client", my son, doesn't want me to take time for them now: he wants results, and I am responding to his wishes. You have my word that I'll get Agile-ized after we reach a working version 1 (or 1.1 ...). I promise :-) Thanks to you and Colin for spending time on a wretch like me :-), Richard On May 15, 7:00 pm, Marnen Laibow-Koser <[email protected]> wrote: > RichardOnRails wrote: > > [...] > > > > > But the two new fields in the expenses table (added via migration) are > > not reflected in the four app\views\expenses files. I can modify > > these four files manually with ease. But some book I perused led me > > to think that two tools would do that for me automatically: > > > first: ruby script/generate model expense > > then: ruby script/controller expense > > > If they'd do the job (which was my original post) of adding CRUD > > elements to my existing CRUD, then I'd like to employ them. And I > > could just employ them and learn right away that they worked or not. > > If not, I could easily recover my previous state. > > Not quite. You do not need to change your model at all -- it will > figure out that the extra DB fields are there. > > script/generate model and controller will not help. script/generate > scaffold might, but you're better off modifying your views manually. > > [...] > > > The > > question about whether I use git or my external hard drive are > > tangential to the issue I'm dealing with. Likewise, whether I use > > formal or ad hoc testing > > Not really. Smart version control and smart testing are essential to > smart development: they give you the freedom to make bold changes with > confidence, and to roll back changes that don't work. Without both in > place, you're just hacking. > > Best, > -- > Marnen Laibow-Koserhttp://www.marnen.org > [email protected] > -- > Posted viahttp://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 > athttp://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 [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.
