Post History

I have raised this discussion in the past, particularly in the context of "one database per community" vs. "one database per instance". We are currently in "one database per instance", where moving a question between communities ("migrate" in SE terminology) would really be only very slightly more complex than moving between categories. However:

* There is general consensus that *long-term* we should be in "one database per community" in order to handle high loads better (and other reasons). A migration in that setup will be more complex, so building it now "easy" would result in a feature that would require some serious (though not insurmountable) work later.
* Until we have a high volume of questions (at which point, we may really want to have the multiple databases), the need to migrate will be relatively minimal. I could see, for example, an "outdoors photography" question being migrated from outdoors to photography. But we don't have, for example, the issue of migration between a general programming site and specific computer languages, or between linguistics and specific human languages, or woodworking to DIY, etc. simply because we don't have most of these communities (yet).

So it is a feature I'd like to see, but, despite my original thoughts on the matter several months ago, not something I think we need any time soon.