Comment on I'll just be a quick 3h

PizzaMane@lemm.ee ⁨1⁩ ⁨year⁩ ago

• ChickenLadyLovesLife@lemmy.world ⁨1⁩ ⁨year⁩ ago

  My all-time favorite database table was a table named STATE, meant to store all US states. It had 531 rows.

  source

  • outcide@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Relatable. 🤣

    source
  • reverendsteveii@lemm.ee ⁨1⁩ ⁨year⁩ ago

    well, there’s confusion, paranoia, agitation and so many others…

    source
  • psud@aussie.zone ⁨1⁩ ⁨year⁩ ago

    I have been trying to get people in my area to make their new table generically named, since it’s going to be the only table that can map a date range to a different date range, but I’m on holidays now, and they can’t imagine anything other than their little project needing this table, so it’s going to be named for this one project, and it’s columns will be named for the specific data they’ll hold :(

    source
  • Melatonin@lemmy.dbzer0.com ⁨1⁩ ⁨year⁩ ago

    Confusion … Your medical condition Disorganized

    source
• peyotecosmico@programming.dev ⁨1⁩ ⁨year⁩ ago

  I’ve been there and you know what’s worse about it? When you fix it only you or a handful of people notice the astronomical labor you did.

  “It worked before why did you change it? You are just doing busywork”

  source

  • PizzaMane@lemm.ee ⁨1⁩ ⁨year⁩ ago

    Yeah. Luckily the work I am doing is to fix some really bad work that the entire company has been complaining about. So once it’s fixed it will hopefully be a little bit more recognition than that. Plus my boss is pretty level headed.

    But who fucking knows? There is always the likelihood that people will say things along those lines. And it ain’t my job to fight them on that.

    source
• SaintWacko@midwest.social ⁨1⁩ ⁨year⁩ ago

  How about a date stored as an integer?

  source

  • PizzaMane@lemm.ee ⁨1⁩ ⁨year⁩ ago

    No, we have worse. Dates sometimes stored as strings, sometimes as datetimes sometimes as integers. There is no consistency, logic, or forethought to the schema.

    source