3 ms·
Is this "just" them not knowing DB isolation levels, or some ORM "layer" rug-pulling from under them? To me ORMs in general have often too many layers of impli
by ElectricalUnion 3y ago
Is this "just" them not knowing DB isolation levels, or some ORM "layer" rug-pulling from under them?
To me ORMs in general have often too many layers of implicit and surprising behavior.
And in a vain attempt to hide their ugly and complex faces, often the situation is made even worse by putting more "layers" in front of them.
Now besides being a specialist in your language, you also need to have somewhat deep knowledge of your DBMS, your DBMS driver, your ORM and in all the layers someone put in front of the ORM, just to not shoot yourself on the foot in a spectacular fashion.
- dathinab 3y ago> Is this "just" them not knowing DB isolation levels yes in the cases where I had been working with an ORM in recent years it where "thin" ORMs which didn't really change anything about transactions/isolation levels nor had any abstractions which seem like they might do additional synchronizations or anything like that (they where mainly query builder + some small amount of ORM parts)