4 ms·
The closest that many have come to is to develop ORM libraries. LINQ + EntityFramework Core is my favorite.
by kumarvvr 5y ago
The closest that many have come to is to develop ORM libraries. LINQ + EntityFramework Core is my favorite.
- mike_hock 5y agoHe said better than SQL.
- kumarvvr 5y agoTo me, ORM code is better than raw SQL. But, a lot many applications can be developed without really knowing the depths of SQL with help of the ORM itself.
- m_mueller 5y agoIs it? All that's ever worked for me with ORMs are simple CRUD apps that don't require referential integrity. We currently need to support one built on Django/ORM where this isn't the case and e.g. deleting an object can require deleting thousands of others.... which the ORM helpfully renders into thousands of queries and can take you half an hour. Luckily the creators soon decided to switch off all timeouts....
- sebmellen 5y agoI have had amazing luck with Prisma.io on the oracle side
- setr 5y agoLINQ is a much nicer SQL IME, at least for CRUD operations — but I generally don’t use the “objects” part of it except for very rudimentary insert/deletes. However group by specifically seems to be a hack, and it falls on its face in weird ways almost every time I use it. I’m not sure how much I like it’s “AST rewriting” model, but it works great when it works. Just the LET command alone justifies it
- xupybd 5y agoI'm normally not a fan of ORMs but I've had good experiences with Entity Framework. I really like the automatic migrations. For small apps and a single dev it hits a sweet spot. I find .Net really good at being kitchen sink included and business ready. If you're making internal small apps I've yet to find a better platform. Especially if you're in an MS Office heavy environment.