Controllers shouldn't be broken if the database is off, if they don't use it. Could it be they're implicitly using the database, for sessions or something of that nature? If that's the case, you might be able to implement your own more robust session handler which deals with absent DB errors. Or perhaps eschews the database all together, and uses something like a high availability memcache or redis cluster.
Regards Jon -- You received this message because you are subscribed to the Google Groups "merb" 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/merb?hl=en.
