I don't generally follow the "whatever works..." approach because there is usually a best practice. That said, I want to avoid the global variable because having $tidbit = Tidbit.random declared in my application.rb broke my migrations. Running migrations from version 0 when the Tidbits database doesn't exist caused the db:migrate to fail because the line of code was still being executed and the Model was attempting to access a table that didn't exist.
I'll keep reading, but I'm sure there is a logical way of accomplishing this that I'm just not yet seeing. Thanks. On Feb 21, 4:41 pm, Eric <ericgh...@gmail.com> wrote: > So why not use that, then? Whatever works... > > Also, you might brush up on MVC and beginner's Ruby as far as "setting > variables in models" > go:http://wiki.rubyonrails.org/rails/pages/UnderstandingRailsMVC > > On Feb 21, 12:45 pm, ericindc <ericmilf...@gmail.com> wrote: > > > Title pretty much explains it. I'd like to set a variable the stores > > a single Model object inside of application.rb since it will be used > > on every single page. I've tried both class and instance variables, > > but to no avail. The only thing that worked so far was using a global > > ($) variable. > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
