I don't have a coding question but more of a structure related one.
If I had a site that say for example allowed a user to sign up, login, and manage finances, or a family photobook or whatever.(the job that the front end is performing is irrelevant) If I have multiple users registering and creating there own accounts then what would be the correct way to store that data? I assume you would not have a single table with different users data together so would it be proper to create a single table for user logins then automatically create a new table exclusive to each new user that would then hold the data related to there personal login?
Take a online check book for example, I would have a table that manages user logins then during the registration process it would automatically create a table for that user to hold all the data entries for their own check book. is that correct? What if the data requires multiple tables to manage one particular users data?
Also does anyone have any good links on proper database structure I could check out? Not knowing correct terminology is hindering my searches.
Thanks in advance!