Millie(let)

if you write a schema so that username is a primary key, thus making it impossible to change usernames until that's fixed (which is not at all trivial to do)

I will personally come to your house and bite you

You must log in to comment.

in reply to @yaodema's post:

Starra @Starra4/27/2024, 9:17 PM

FA's pretty infamous for this

Yaodema @yaodema4/27/2024, 10:18 PM

yes, however, it's a problem with a lot of the web, and even for internal systems. it's easy to recognize on sight, at this point

Starra @Starra4/27/2024, 11:04 PM

Oh yeah definitely - was just the first well-known example that came to mind :P

Lapis the Nevrean @lapisnev4/27/2024, 10:29 PM

... oh is THAT why

Starra @Starra4/27/2024, 11:06 PM

Pretty sure, yeah - if you look at the url of image files directly, they all have the username of the uploader in the filename itself

Birdout: Paradise @SomeEgrets4/27/2024, 9:25 PM

is that a promise?

Yaodema @yaodema4/27/2024, 10:18 PM

only for those who won't enjoy it

frankie boyle's beanbag chair of death @micolithe4/27/2024, 9:28 PM

only an idiot would take a user-enterable value as a primary key :)

(you can create a uniqueness constraint on username without it being a PK)

Yaodema @yaodema4/27/2024, 10:19 PM

mmhmm, it's not even hard! and people are repeatedly told not to do this very specific thing and to use a numeric primary key instead! so why does it keep happening

frankie boyle's beanbag chair of death @micolithe4/27/2024, 10:25 PM

usually it boils down to two things:

inexperience
thinking you know better than industry standard concepts like an auto-incrementing primary key field.