Hey All,
Just a general "seeking advice" question here:
I'm building a database app that stores potentially huge text-based documents in the database (it has to be done this way to maintain the structure and relations etc etc).
In terms of the end product, ie. searching this content etc.. would it be better for me to shove all this content into one big table or is it smarter to have the application build individual tables for each document?
When people are searching they will only be searching SOME of the documents so I figured the individual tables approach would at least cut this down a bit... but is there some hit MySQL takes from searching multiple tables that I'm not aware of?
Any advice, as always, is much appreciated =)
- nutter
Just a general "seeking advice" question here:
I'm building a database app that stores potentially huge text-based documents in the database (it has to be done this way to maintain the structure and relations etc etc).
In terms of the end product, ie. searching this content etc.. would it be better for me to shove all this content into one big table or is it smarter to have the application build individual tables for each document?
When people are searching they will only be searching SOME of the documents so I figured the individual tables approach would at least cut this down a bit... but is there some hit MySQL takes from searching multiple tables that I'm not aware of?
Any advice, as always, is much appreciated =)
- nutter