27
gorsamp
7y

Once a month I get a crash for the stupid PHP site I am in charge of because the guy who made the database made the primary key of a table a varchar. It is a number 99.9% of the time but the dumbass customer always enters one entry with a string cuz the dumbass db Dev let them. I emailed the dumbass Dev telling him he is stupid and he said it is part of their philosophy. I told him I still think he is stupid so he emailed my boss.

I emailed him again telling him he is stupid.

Comments
  • 7
    If I had their email I might also call them stupid πŸ™ƒ
  • 1
    @Ashkin I'd love to brigade this fool but this my first salaried position, I have PLAAANNNSZSSZSSS
  • 4
    "It's part of our philosophy" I need to use that excuse more often!
  • 2
    Pleeeease share his email once it doesn't affect you anymore πŸ˜‚πŸ˜‚
  • 2
    Sounds like the validation is the issue? I don't see what's wrong with a varchar PRI, what if you wanted to enforce GUIDs to avoid consecutive account IDs?
  • 3
    @Dotwo the problem happens with generated queries. When your library sees only numbers and it asks sql for the user by his id or an inner join, an error is returned because 'Evelyn' cannot be cast to int. So I have to force the type all over the place or other random shit. I would explain further but in short no customer uses anything but numbers, they must be typed in so they're not guids, it's usually 4 digits.
Add Comment