On Mon, Aug 30, 2010 at 2:46 PM, Platonides Platonides@gmail.com wrote:
We already have a painfully long list of tables, and new tables also mean more problems for deployment.
It's fine to have lots of tables, that's usual in complicated relational databases. New tables are trivial to deploy, it's alterations to existing large tables that are hard. (Altering user_groups would probably be easy to deploy too, since an alter should only take a second or two, so you likely wouldn't have to bother taking slaves out of rotation to do it.)