LINQ to NHibernate

Best Quote from Oren on DNRtv:

Oren: “This is HQL, Hibernate Query Language. It is similar to the SQL look but it has more OO notation. …”

Carl: “Starting to look like LINQ a little bit.”

Oren: “Yes, it looks like LINQ, but this is string. This is string but what will happen is once LINQ passes beta status me or someone else from NHibernate community will write a LINQ adapter for NHibernate. I don’t know the exact name. It actually isn’t very hard. I talked with at TechEd isreal last year and it doesn’t look very hard at all to do this. The concept is very much the same.”

So, learn and use NHibernate (or Castle ActiveRecord) now. Don’t worry or fret about LINQ, DLINQ, LINQ to SQL, LINQ to Entities, LINQ to DataSets. The beauty of LINQ will be available for NHiberate. LINQ is not the death of NHibernate.

NHibernate is a vast library with many extensiblity points. NHibernate exists today, it has proven itself for years. Its intricacies are well understood by the community and there is excellent documentation surrounding it. Now I’m sure that LINQ to SQL will have reams of docoumentation as most Microsoft products eventually do. But, LINQ to SQL is for Microsoft SQL Server only. NHibernate has mappings to MSSQL, PostgreSQL, Firebird, MySQL, SQLite, even Access, and probably many others. By leaning on NHibernate you are assured a high level of compatibility with any RDBMS. Some organizations value this. I value this.