Is NHibernate in Action for NHibernate V1.2 still relevant in October 2009?

Question

Staffed Manning is working on "NHibernate in Action" for $ 10. NHibernate In Action was released in February 2009 for NHibernate V1.2. NHibernate currently corresponds to version V2.1. Will the V1.2 book be relevant enough to apply to the current release of NHibernate. I do not want to spend my time and money on a book about outdated or non-essential features.

I am a complete NHibernate noob, but I am no stranger to the general concept of ORM.

Update:

I bought a book, and from the small amount I read, the V2.x series was in beta when the book was released. The authors of the book note some differences in configuration between 1.x and 2.x. From what I have read so far, I recommend this book to anyone who wants a book on NHibernate.

Answer 1

Yes, it will still be relevant. You can find basic definitions of ORM systems in it.

There are also many examples about displaying and solving common problems, such as inheritance, collection matching, caching, etc.

Answer 2

After some digging, I found this post that is related to this blog , which actually gave a few bits of detail on NH2.1, but not sales. This is the main problem with which, it seems to me, NHibernate - they are not sold on their own, but they like to "keep her in the family", you need to dig through the blogs of the developers.

In any case, release notes are where they tell you. releasenotes.txt contains the whole story and here are some selections from 2.0 and 2.1:

• .NET 1.1 is no longer supported
• Nullables.NHibernate is no longer supported (use .NET types with valid values)
• NHibernate.Expression namespace has been renamed NHibernate.Criterion
• <nhibernate> in the App.config application is no longer supported and will be ignored. The configuration diagram for the configuration file and App.config is now identical, and the App.config section name is:
• <hibernate-configuration> have a different schema and all cheked property names
• Configuration properties are no longer prefixed with "hibernate." If, before you specify "hibernate.dialect", you now specify only "dialect"
• NHibernate will return long count (*) queries to SQL Server
• Different spaces moved between namespaces
• Various classes have been renamed (to match the names of Hibernate 3.2)
• AutoFlush will not occur outside of a transaction. Database operations are never required. All communication with the database must occur within the transaction, regardless of what you read or write. (This may affect what you read in the book; see this question )
• case when ... then ... else ... end in select clause

There are about a hundred others, but nothing will affect you if you are not trying to upgrade from 1.2 to 2.1.

Answer 3

I just bought a book, and I find it very useful and relevant. In any case, most of the important material is conceptual. My big problem is that I use fluent nhibernate, so many of the XML elements and attribute and configuration contents in the book are not that important to me.