TechCodex@programming.dev to Programmer Humor@programming.devEnglish · 11 months agoHours of workprogramming.devimagemessage-square48fedilinkarrow-up1908arrow-down118
arrow-up1890arrow-down1imageHours of workprogramming.devTechCodex@programming.dev to Programmer Humor@programming.devEnglish · 11 months agomessage-square48fedilink
minus-squareKalash@feddit.chlinkfedilinkarrow-up34·11 months agoI’m in the exact same boat right now. Also this change from 1:1 to 1:n entity was like one “minor” feature in a rather larger list of feature requests. It so far has caused more work then all the other features combined.
minus-squareAggressivelyPassive@feddit.delinkfedilinkarrow-up19·11 months agoAnd months later you’ll find out, that your change completely fucks over some internal optimizer statistic and causes the DB to turn into lava. I definitely don’t know that, because of several hour long outages and millions of lost revenue.
minus-squareFuntyMcCraiger@sh.itjust.workslinkfedilinkarrow-up7·11 months agoOr worse, it was an n:1 and they want it n:n
I’m in the exact same boat right now.
Also this change from 1:1 to 1:n entity was like one “minor” feature in a rather larger list of feature requests. It so far has caused more work then all the other features combined.
And months later you’ll find out, that your change completely fucks over some internal optimizer statistic and causes the DB to turn into lava.
I definitely don’t know that, because of several hour long outages and millions of lost revenue.
Or worse, it was an n:1 and they want it n:n