Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Well, adding constraint relationship to user table and cause an error when data deleted is actually good, because it's try to prevent data inconsistency. The solution to this problem is either make constraint on delete cascade or implement soft delete. which is better its depend on your project requirements.
-
@BimaAdi the problem is its not supposed to be there. It was a copy and paste mistake. Like the 2 table should have no relationship at all. Hahaha. But my boss believes that the error was our feature. HAHAHAHA
Found this in our codebase, apparently one of my co-workers had written this
Conversation with my Boss
B: Are u a hacker?
M: No
B: We need a hacker?
M: Why?
B: Because X department w...
Hey read this. This shit is funny. HAHAHA
I was fixing a bug right. The bug was throwing InverseOfAssociationNotFoundError in our rails admin page when deleting a user. So the director of engineering called and we had an argument because he was insisting that the error InverseOfAssociationNotFoundError is OUR IMPLEMENTATION. HAHAHAHAHA. my goodness. I showed him that the error comes from the constraints when deleting a user. A table has no relation to the user table but my senior added it anyway for some reason. I was mad and laughing at the same time because I showed him the documentation and the simple fix. These idiot keep flexing his 30 years of experience. HAHAHA
rant
boss
wtf
senior