| Web Design & Programming Building websites, coding scripts or developing apps? html, css, javascripts, ajax, php, asp, java, c+, C++ and other geeky info is here. |
 |
| | LinkBack | Thread Tools | Display Modes |
08-01-2009, 02:10 PM
| #1 (permalink) |
 Status: Junior Member Join Date: Aug 2009 Posts: 1
 |  Is it a good idea to design only one database for all web products(subdomains)... ...with many many tables? I'm developing a website with six products. I want to design seven databases, one for each, and the 7th database is a common database shared among the six products.There is a problem, I often need cross- database operations. I want to create some stored procedures/routines and some of them need cross-database operations and I don't know how to do it.It is MySQL. Is it a good idea to design only one database with many many tables? What are the advantages and disadvantages? For example, on the website of yahoo.com, there are so many web products, Yahoo! on the website of google.com, there are so many products,Google Web search, Google shopping, Google maps, gmail, etc. There is one website(one domain) with many subdomains. One owner will own the entire website. Answers is one of them. If I design one database with many tables, how can I group these tables up with schema? The database is MySQL. I was surprised the concept "database" in phpMyadmin is the same as the concept "schema", which is the very parameter in mysql_select_db(). So what do you mean by "database" or "schema"? I was surprised the concept "database" in phpMyadmin is the same as the concept "schema", which is the very parameter in mysql_select_db(). So what do you mean by "database" or "schema"? |
|         |
|
| Thread Tools | |
| Display Modes | |
| |
Linear Mode
