Sql – Most complete ORM with LINQ support

linq-to-sqlormsql

I'm looking for an ORM that offers complete or near-complete LINQ support.

LINQ to SQL
– Supports about everything inside of LINQ (.Contains, Math.Log, etc)
– Cannot eager load relationship properties without creating a new datacontext

ADO.NET Entity Framework
– Terrible LINQ support (lots of missing features).
– Great mapping features
– Can eager load on demand with .Include methods on an ObjectQuery<>

LightSpeed
– Great LINQ support missing some features (.Contains within a Where)
– Some of the SQL generated is very inefficient.

None of these seem to fit just perfectly, I honestly wish I could take bits and pieces from each. I personally really like ADO.NET EF except the features it is missing make it just frustrating to use.

I know some people praise NHibernate up and down and I'm not knocking it but I spent today trying it out and it's ok but it's LINQ support is not that great.

Best Answer

NHibernate with Linq to NHibernate

Syntax:

ALTER TABLE {TABLENAME} 
ADD {COLUMNNAME} {TYPE} {NULL|NOT NULL} 
CONSTRAINT {CONSTRAINT_NAME} DEFAULT {DEFAULT_VALUE}
WITH VALUES

Example:

ALTER TABLE SomeTable
        ADD SomeCol Bit NULL --Or NOT NULL.
 CONSTRAINT D_SomeTable_SomeCol --When Omitted a Default-Constraint Name is autogenerated.
    DEFAULT (0)--Optional Default-Constraint.
WITH VALUES --Add if Column is Nullable and you want the Default Value for Existing Records.

Notes:

Optional Constraint Name:
If you leave out CONSTRAINT D_SomeTable_SomeCol then SQL Server will autogenerate
a Default-Contraint with a funny Name like: DF__SomeTa__SomeC__4FB7FEF6

Optional With-Values Statement:
The WITH VALUES is only needed when your Column is Nullable
and you want the Default Value used for Existing Records.
If your Column is NOT NULL, then it will automatically use the Default Value
for all Existing Records, whether you specify WITH VALUES or not.

How Inserts work with a Default-Constraint:
If you insert a Record into SomeTable and do not Specify SomeCol's value, then it will Default to 0.
If you insert a Record and Specify SomeCol's value as NULL (and your column allows nulls),
then the Default-Constraint will not be used and NULL will be inserted as the Value.

Notes were based on everyone's great feedback below.
Special Thanks to:
@Yatrix, @WalterStabosz, @YahooSerious, and @StackMan for their Comments.

Best Answer

Related Solutions

.net – Entity Framework vs LINQ to SQL

Sql – Add a column with a default value to an existing table in SQL Server

Syntax:

Example:

Notes:

Related Topic