Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Badpointer83308dI think LINQ provides data structures that sql doesn't have.
gorsamp2324308dThat's just not fair. What if you present a list of objects and then you only update those marked to be updated? Unless you program every arbitrary change into SQL it can't be aware of things that Linq can at runtime.
AleCx0412465308dLmao get eeem
thoxx1839307dwho uses linq to sql in .NET nowadays?
Badpointer83307dMany dot Net developers. LINQ itself is a great tool to filter out large data sets that doesn't have to connect to a Database. It just easier to write for C# developers writing sql queries with LINQ and quicker to debug than just passing a string value then manipulate your data. It's just a helpful tool for dot NET developers.
Don't mix LINQ to SQL, LINQ to Entities, EF & Co
LINQ to SQL and Entity Framework are two different OR Mappers.
Linq2Sql is dead for many years (we used it like 10 years ago). No one uses Linq2Sql nowadays. Everyone uses Entity Framework or Entity Framework Core (or Nhibernate...whatever).
Linq to objects is for querying your objects. Linq to entities is for querying your EF model.
So yeah ... not using LINQ at all would be really stupid. But LINQ != LINQ to SQL ;-)
mzeffect1922307dSQL is for people who can't write LINQ 😀 or are stuck in an unfortunate stack that doesn't let them use LINQ. I would always prefer using some kind of ORM or equivalent to ease the hard coupling with a particular database implementation.
Your Job Suck?
Take a quick quiz from Triplebyte to skip the job search hassles and jump to final interviews at hot tech firms
Get a Better Job