问题
My understanding is that MySQL is intended to have tables with millions of rows. I am looking for a database system designed to have millions of relational tables. Am I correct in my understanding that the way MySql queries data makes it inefficient for that sort of an implementation? It is for a long-term, user-driven project, so extensibility is a must.
Thanks!
EDIT: Due to the immediately negative reaction, I'll explain myself. "Millions" of tables would be an issue if the project lived to accumulate a strong user base in time. It would implement an edit system similar to that on Stack Overflow; I considered a variety of solutions, and decided the one I liked best was one using a relational table for each offshoot of edits. I assumed there was some database framework designed for that sort of thing. Is this really considered "bad" architecture? Why is it not just an abnormal type of architecture? What is "wrong" with doing something that way?
回答1:
You could always look towards a NoSql DB: From: http://nosql-database.org/
"NoSQL DEFINITION: Next Generation Databases mostly addressing some of the points: being non-relational, distributed, open-source and horizontally scalable."
Edit: Scalable is what I was shooting for..
Suggestion: http://www.mongodb.org/
Edit: Interesting idea about data versioning: Ways to implement data versioning in MongoDB
来源：https://stackoverflow.com/questions/17310003/database-alternative-to-mysql-made-for-millions-of-tables