4

I fucking hate entity framework.
It turns 10 mins of work into fucking hours of stress and bloat and shit.

It’s the one thing in dotnet that I cannot fucking stand.

Literally did a bit of work in 10 mins (using ef I might add), but because it’s not the”ef way” I need to create an extra table/class and then fuck about mapping the relationship in a complicated way to do what I had just done in only a few lines of code with one table.

Spend over an hour trying to get it to understand the relationship before I gave up for the day. Fuck it

Comments
  • 0
    what exactly were you trying to achieve?
  • 0
    Relationship mapping in EF is the most confusing part. I consider myself pretty competent with EF and still trip on this aspect of it.
  • 0
    This is exactly how I feel about spring.
  • 1
    ef is a shit solution in search of a problem, shoehorning it into projects just because a manager read about it on the internet does absolutely nothing useful and makes everything a fucking nightmare to work on.
  • 0
    @tosensei what I actually needed was just a table with two fields, which make up a compound key.
    What I ended up doing was defining a parent and child with a one to many relationship.
    Partly cos the team insisted on that, I had the simpler version working.

    But then I spent ages figuring out why I was getting orphaned children and didn’t realise I had to enable cascading deletes, even tho I’m never deleting the parent.

    Having spent the last few years doing mongoDB, what I once new about EF (which was before the core version) now seems alien.
  • 0
    @TrevorTheRat that's wird.... composite keys are very easy in EF
Add Comment