|
|
Posted by Martien van Wanrooij on 05/11/05 08:44
"cover" <coverland914 @ yahoo.com> schreef in bericht
news:1115784541.db02b61609020993f871cd980906dbc7@teranews...
> If you're writing many databases that aren't necessarily associated
> with each other (ie parts, vacation days, how you like your steak
> done, and school you attended, etc; as examples), does it make more
> sense to have one database name and several tables for the data topics
> above OR multiple databases since they aren't associated with each
> other?
The company where I hosted my domain name charges an additional fee for a
mysql database. So I have chosen for one database, when I would need to
create more "subdatabases" (i.e. groups of tables that according to their
behaviour could have been separate databases) I could work with prefixes to
the tables so you can still use almost the same table names if necessary
like db1_members, db2_members and db1_results, db2_results etc. I think
there must even be a trick to transfer one "table group" to a new database
when that will be necessary some day.
But be aware that I am relatively new at this topic :)
Good luck,
Martien
Navigation:
[Reply to this message]
|