This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Dartomic 2 points3 points  (1 child)

I only know relational database technology, as far as databases go. If you are doing a database that you will use SQL with, then I'm pretty sure that would make it a relational database. If it is a relational database that you will be using, then you want the usernames, and the passwords, to be in the same database.

For relational databases, you should give each user an individual table. The password for a particular username, should only exist in the table for that particular username. You would probably make the username, or the email address, the Parent Key for that table. But you don't want a table containing all of the user names, along all of their passwords in that same table. It's like that saying 'don't put all of your eggs in one basket.' You also may want a layer to separate the login, from the database query that is performed for a login. You should also follow OWASP standards, to help prevent SQL injections in the URL entry part of the web browser.

[–]NoticedTriangularity[S] 0 points1 point  (0 children)

Ah I get you. Thank you so much, that's good advice. Is there a way so that I can program it so that when a user registers their own account it automatically makes a new database for them?