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.
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.
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.
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”
How about a date stored as an integer?
Edit: and I’m not taking about a timestamp
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.