O.K. I've been agonizing over this for some time now,
in this website i'm building, every registered user is gonna have
some data that he can review add update delete.
what would be the best way to store this data? in sql?, so that we have this one huge
table where we have one column that identify's the user (on average each user will have after a while between 1400 to 1700 records),
2nd option with sql is create different table for each user?.
in either case the database size can potentially be pretty big, which will horribly effect hosting budget!
or should i create an xml file for each user (there will be no trouble of multiple users trying to access same file). this will be better for hosting budget, however i don't know how will it effect the system performance to have so
many files on it?, also accessing and retreiving data from many xml files at once might strain the system (because it
seems like to read the xml, it loads the whole file to the memory ram right?)
so what should i do?
thx a bunch nati.