At work, I am currently dealing with a table that has no primary key, no foreign key, duplicate (almost) serial numbers, booleans stored as strings, and so on. It's a nightmare of a table.

Entity framework is acting like I'm on meth for using such a table.

[–] peyotecosmico@programming.dev 2 points 1 year ago (1 children)

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"

[–] PizzaMane@lemm.ee 1 points 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.

[–] SaintWacko@midwest.social 2 points 1 year ago* (last edited 1 year ago) (1 children)

How about a date stored as an integer?

Edit: and I'm not taking about a timestamp

[–] PizzaMane@lemm.ee 1 points 1 year ago* (last edited 1 year ago)

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

It's rough.