I noticed Rails reloads my classes on every request. My database can't handle that. My database depends on classes maintaining their identity. That is, given a class "Person", Person.object_id must not vary across requests. Is there a way to turn off this "reload per request" behavior? And why does it do this in the first place? Seems rather strange.
Thanks. Michael On Sep 7, 8:41 am, "Bill Walton" <[EMAIL PROTECTED]> wrote: > Hi Michael, > > Michael Allman wrote: > > > I'm developing a rails 2 app with a custom database for persistence > > (not activerecord, not sql). I need to open the database once at > > application startup and close it once at application shutdown. I > > figured out how to add an application startup hook by putting a script > > in config/initializers. I can't figure out how to add a shutdown > > hook. Can someone point me in the right direction? I really need to > > close the database properly at shutdown time. > > You may be misunderstanding one of the basics of Rails applications. Rails > apps are not daemons that start up and then sit there running, waiting for a > next request. A Rails app exists for exactly one request - response cycle. > It starts up when it receives a request, and it shuts down after it delivers > its response. When it receives another request the cycle is repeated. > Easiest thing in your case could be to define a start up method and a shut > down method. Your start up method could be called based on a global or a > class singleton. Your shut down method will probably have to be invoked > explicitly though. > > HTH, > Bill --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
