5

I made a bad design decision on the DB level, I made 1 NON-NULL column so i can avoid 2 NULLABLE columns
Small thing, but over a couple of years it's now bed-rock code and Projects, Services, API layers, all have to deal with "Am I a URL or an EntityID?", n on-demand derivation across Projects (or even param-passing) has started to birth bugs T__T
If it were something small like a log I'd ignore, but it's core to how content is stored n entire analytics is tied to it

It's theoretically an easy fix, BUT IT'S SO DAMN TEDIOUS. I've to make a LOT of things to live together and migrate some data, if even 1 portion is messy, there'll be silent failures (:
I've been putting it off for a week now coz my mind actively avoids doing it. Kill me

Comments
Add Comment