You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The userlogininfo table connects a user ID to a LoginInfo, but I can't see why a separate table is needed for this. This is not a many-to-many relationship - each LoginInfo should belong to a single user (although a user can have several LoginInfos if they link accounts from different providers). Shouldn't it be sufficient to store a userID field in the logininfo table?
The text was updated successfully, but these errors were encountered:
The
userlogininfo
table connects a user ID to aLoginInfo
, but I can't see why a separate table is needed for this. This is not a many-to-many relationship - eachLoginInfo
should belong to a single user (although a user can have severalLoginInfo
s if they link accounts from different providers). Shouldn't it be sufficient to store auserID
field in thelogininfo
table?The text was updated successfully, but these errors were encountered: