I assume that your initial case is working: New web session hits the web server, application sees "new" and uses master database. User logs in (verified against master) and is hooked up to the correct database.
Not knowing any of the details of your login/logout or session management, it sounds like after logging out, you aren't clearing enough data out of the session so that the same browser session would be recognized as "new" (i.e., the same as a totally new browser session) when you try to log back in. -- 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 -~----------~----~----~----~------~----~------~--~---
