3 ms·
A) it's exceptionally boring Perhaps as a result of it being so exceptionally boring that it's so error-prone. If you forget to wire something up by hand (espe
by MartinCron 15y ago
A) it's exceptionally boring
Perhaps as a result of it being so exceptionally boring that it's so error-prone. If you forget to wire something up by hand (especially if its nullable) and don't notice while you're coding, it can be one of those subtle little bugs that lingers in the background until it really bites you.
Also, you forgot:
D) Difficult and time-consuming to create test automation for.
- drivebyacct2 15y agoYes! At least LINQ-to-SQL gives compile time type checking.
- johnzabroski 15y agoLinq 2 SQL has ambiguous relationship path decision function when deciding how to map the Linq expression tree model to the SQL DBMS's model. Compile-time type checking is very illusory with heterogeneous execution, not only for this reason but also because it is a distributed application and the schema can change.
- drivebyacct2 15y agoAnd I've been bitten by the truth of your statement. It sure beats the pants off writing SQL by hand.
- keithnoizu 15y agoIs LINQ even in favor anymore. I think we're all about the entity framework now which appears to be more or less ORM with an auto update component for references to the orm objects.
- drivebyacct2 15y agoNo, but you still use LINQ style lambda expressions to do more advanced queries involving the EF objects. It's actually a really, really nice blend. If you're doing .NET dev though, take a look at NHibernate. It's been around longer, it's been stable much longer, it has more features... and it actually has a community which is probably EF's weakest point IMO.
- keithnoizu 15y agoI'm old and set in my ways at the ripe-age of 29 and like my sql processed as prepared statements that reside in my data objects. I also curse everytime I see relationships between data that do not boil down to int (size of system's cpu architecture) equivalency checks.