nHibernate still better than EF
-
All these years and revisions later, does nHibernate still offer more?
-
All these years and revisions later, does nHibernate still offer more?
Tim Schwallie wrote:
All these years and revisions later, does nHibernate still offer more?
I wouldn't know, I don't use either. ;)
Latest Article - Class-less Coding - Minimalist C# and Why F# and Function Programming Has Some Advantages Learning to code with python is like learning to swim with those little arm floaties. It gives you undeserved confidence and will eventually drown you. - DangerBunny Artificial intelligence is the only remedy for natural stupidity. - CDP1802
-
All these years and revisions later, does nHibernate still offer more?
-
I guess recently I miss SessionLess or whatever it was called in nHibernate. I know there's ways to set that up in EF, just a few extra steps. I miss being able to choose the concurrency strategy, ie use this DateTime field, increment this integer field, use sql server TimeStamp, and so on.
-
All these years and revisions later, does nHibernate still offer more?
I have never used nH. However, the latest version EF is just fine, and I have not needed to go elsewhere.
-
I guess recently I miss SessionLess or whatever it was called in nHibernate. I know there's ways to set that up in EF, just a few extra steps. I miss being able to choose the concurrency strategy, ie use this DateTime field, increment this integer field, use sql server TimeStamp, and so on.
I don't do much .net development any more these days, but back when I did, I always preferred NH because I had to support legacy databases. I could map a boolean in my model to a char(1) in the database without having to muck up the model code with mapping information. At the time, EF (5? I think it was?) didn't have that capability yet. Don't know if it has it yet or not.
-
All these years and revisions later, does nHibernate still offer more?
Who cares? Avoid both/all.
-
All these years and revisions later, does nHibernate still offer more?
The problem with NH is the same with many of these frameworks is the lack of documentation and trying to work out how to do things is a frustrating trawl through 7 year old SO threads giving solutions that no longer work with your version. All though this evidently EF's downfall too given this thread. I think people think you just drag things onto a designer with EF and that's all it can do. EF is capable of much more than people think, including custom mapping, having an entity represent data from multiple tables, reusable complex types and all sorts but you really need to get a book on it to appreciate everything it can do.
-
The problem with NH is the same with many of these frameworks is the lack of documentation and trying to work out how to do things is a frustrating trawl through 7 year old SO threads giving solutions that no longer work with your version. All though this evidently EF's downfall too given this thread. I think people think you just drag things onto a designer with EF and that's all it can do. EF is capable of much more than people think, including custom mapping, having an entity represent data from multiple tables, reusable complex types and all sorts but you really need to get a book on it to appreciate everything it can do.
There are A LOT of old farts on this site that still take the horse and buggy to work.
-
The problem with NH is the same with many of these frameworks is the lack of documentation and trying to work out how to do things is a frustrating trawl through 7 year old SO threads giving solutions that no longer work with your version. All though this evidently EF's downfall too given this thread. I think people think you just drag things onto a designer with EF and that's all it can do. EF is capable of much more than people think, including custom mapping, having an entity represent data from multiple tables, reusable complex types and all sorts but you really need to get a book on it to appreciate everything it can do.
Yes, that is kind of how the industry works. Only enough documentation to keep the EU off your back. Write books/online videos/articles/etc to fill in the blanks. Show me the $$$$.
-
I have never used nH. However, the latest version EF is just fine, and I have not needed to go elsewhere.
Best I can say is take a look at NH or it's parent Hibernate. It'll give you an idea where a lot of the EF functionality came from.