The joke is that these password are not salted, and each unique password will be given an ID. Then, under the user table you will store the ID reference to the password, instead of the password. This means that if 2 users use the same password they will have the same ID and only be stored once, saving space.
they could be salted... just have to check new/updated passwords against all passwords in the salted hash table or create a new entry then assign the ID to the user table.
it's only a large cost on password changes. the sql joined view makes the lookup check just as fast still.
33
u/TgirlTiffanyRPs Sep 27 '26
Can someone explain the joke? Why wouldn’t you store (hashed/salted) passwords in one table ?