Strictly for DB Developers


DBA:  Do you want usernames to be unique?
Developer:  Yes

(next day)

DBA: Should passwords be unique as well?
Developer:  No

(later that day)

DBA: Shouldn't we require passwords to be unique?
Developer: No
DBA:  Are you sure?
Developer: <15 minutes of explanation as to why different users are not required to have different passwords, just usernames>

(next day)

DBA:  Your procedure doesn't return a specific error message.
Developer:  It's a security issue, and should only return "Invalid Username/Password Combo."
DBA:  So if they get the username wrong, but the password correct you're not going to display a specific message?

The credit for this message goes to The Daily WTF

Comments (6)
  1. So, what are you trying to say ? That DBAs are stupid ? I don’t think so and this specific WTF item (unlike the majority) looks very unmature and offensive, imho.

  2. Tene says:

    "That DBAs are stupid ?"

    No just that they are susceptible 😉

  3. Not at all, DBAs have their own class. They are the heroes of the the backend.

    This shows the interoperatibility between a DBA and a Developer. I just wanted to highlight the importance of a DBA in a project.

Comments are closed.

Skip to main content