I wanted to know your thoughts on information architecture for MySQL when it comes to a username and password table.
The basic (and common) premise is that a user will need to enter a username and password to access their in-app details. I will need a "users" table for this with two fields "username" and "password" I assume. This is one table.
A second table will deal with in-app objects the user owns (object-oriented tables).
However, unlike in MS Access where you can create a LOOKUP field and therefore duplicate data and make connections, what is the best method to relate user data to user's app data?