Lulers
Learning DB and Identity
Having all of that data in one table would be conventionally safe? I.e the logic credentials, and other data to be used by the backend for nutrition tracking, BMI calculation etc? I was under the impression it would be safer to separate the two, but then again, ChatGPT told me so, and if I learned anything from Terminator, is not to rely on AI
30 replies
Learning DB and Identity
I see, so basically I would create that if I need to edit the generic user table identity would create, but if I will be fine with Identity's generic AspNetUsers and I would just use it's forein key to connect to my UserProfile table (which is not supposed to store any login information, it basically extends the user profile for other data like user age, weight, height etc) and leave it as is
30 replies
Learning DB and Identity
Thank you for your response, What I currently am trying to practice on is creating a DB model for a table called "UserProfile" to hold profile information that is important for backend functionality, but not for authentication or registration. As I understood using the documentation and some ChatGPT is that (and correct me if I am totally misunderstanding that) Identity will automatically create a bunch of tables, one of them being 'AspNetUsers' that will contain all the required fields for the library, and then I can manually edit my UserProfile table to connect the keys between them, as opposed to creating a custom UserInfo table and custom design it to fit the Identity library criteria. I am going to start working on it later after work tonight, so I still didnt get a chance to dive into it in practice and to get an understanding of what exactly I dont understand 🙂
30 replies