On Oct 18, 7:59 pm, Colin Law <[email protected]> wrote: > On 18 October 2011 16:43, Hesham <[email protected]> wrote: > > > > > > > > > > > > > On Oct 18, 7:34 pm, Colin Law <[email protected]> wrote: > >> On 18 October 2011 16:25, Hesham <[email protected]> wrote: > > >> > I have a class variable (@neo) that that get initialized by using > >> > something: > > >> > Graph.connect > > >> > where the connect method will initialize the variable @neo > > >> > Right now I call the Graph.connect method in any other class that > >> > needs to have the variable initialized. > > >> > is there a way to have the variable initialized at the start of the > >> > execution of the app, regardless of point of entry? > > >> You could specify it in a before_filter in application_controller. > >> Then it will get run for any action. > > >> Colin > > > That would work, but is there a way to have it initialized for both > > controllers and models at the start. > > Something like the db yaml configs? > > What do you mean by initialised for a model? > You said that you are initialising a class variable, I assumed you > meant a controller class variable.
A model is a class as well, right? Maybe, I should explain that the variable is actually a connection to an external rest-dd, the Graph model is actually responsible for all interactions with the db. Right now, I check if the connection is set and if not I set the connection. What I would like is to have the connection set at app start. > > Colin -- 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.
