I had thought about making them class methods; that would work. It just seemed more proper for them to be constants.
I have at least one more place where I'm doing 'class-load' time DB access. I'll have to see if I can make it 'lazily evaluated'. Since the prevailing thought is that a Rails app isn't fully initialized until the migrations have run (thus the caution against using models in migrations), I wonder if it would be possible to programatically distinguish between a Rails env in which migrations had been fully run and otherwise. Thanks for the response. Brian -- Posted via http://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 at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
