16

To the cunts who use single character aliases for their SQL queries table joins... Suck my throbbing dick till you choke on it and die....

That's all... back to work

Comments
  • 6
    Yes, he/she should use full table name as ails 😂. What your suggestion?
  • 2
    Take that --
  • 5
    My colleagues sometime uses aa instead of just a, is that better?
  • 7
    What? You want me to write tableX.id tableY.field instead?

    Orders o
    OrderItems oi
    Products p
    Customer c

    Not seeing much confusion here.

    Maybe when there’s multiple tables with the same starting letter(s) but then you’d use more then 1 letter with something more meaningful.
  • 1
    @devTea show 'em this rant and if they are intrigued by my offer, I'm happy to oblige.
  • 1
    @C0D4 for short queries.. no probs.. for complicated and long SQL scripts with sub-queries and shit... it is a different story.
  • 1
    @zotigapo come here... get in line... lemme slap you... with my throbbing dick 😆
  • 0
    For sub queries just use p1 p2 etc. What could possibly go wrong? 🤔😱
  • 0
    Couldn't agree more. I once had a senior dev above me who used one or two letter abbreviations for database tables, and combined those with a really complicated naming schema for results. OTOH I would just name a list of pupils, you know, "pupils". The senior complained "your code is too descriptive" and the other dev in the team agreed.
    I don't work there any more. If you wanna high five each other for writing the most unreadable code, you'll have to do so without me.
  • 0
    Don’t offer these kinds of value propositions, I need to know whether that dick be worth your wrath. 👀
Add Comment