u/Numerous_Economy_482

Please don't judge me, I'm not applying for a DB job, I just want to get basic design principles. If possible very example driven, why to use one to many in this case, or not to use. I know that every field needs years to master, even what I mentioned, I don't want to master it :-)

So any course suggestions?

[Edit] SQL is not a huge problem, I want to know things like, should everything related to a user be a huge table? Should I put flags about his password in the same table as his address. Or separate tables based in some principles?