I know it can be convenient for a programmer to group different sets of tables into different databases. Is a computational benefit to doing this?
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I know it can be convenient for a programmer to group different sets of tables into different databases. Is a computational benefit to doing this?
There’s no advantage or difference that comes from putting MySQL tables in different databases, except that databases provide a kind of namespacing. That is, you can have two tables with the same name, in different databases.
Otherwise, as long as the databases are managed by the same instance of MySQL Server, you can do anything as if the tables are in one database, including
JOINand evenFOREIGN KEYreferences between the tables.See also “MySQL: Many tables or many databases?“