tag:blogger.com,1999:blog-8389214606941174691.post9071505306005201353..comments2024-03-23T02:47:30.648-07:00Comments on Tech Talk: Entity Framework 4 - The light of .Net ORM dawn?elLocohttp://www.blogger.com/profile/04685538094487060639noreply@blogger.comBlogger9125tag:blogger.com,1999:blog-8389214606941174691.post-82316401885973685712011-01-30T13:01:21.361-08:002011-01-30T13:01:21.361-08:00As far as I looked I found NHibernate is by far th...As far as I looked I found NHibernate is by far the most feature complete. 2 Month ago I used NHibernate 3 Beta 2 with LINQ Support and I really loved it. It also gives you the opportunity to use your SQL and does the mapping for you. I think ORM are basically popular for a reason. In a scenario where you want to store an object to a database they can be really helpful. Let them create the tables for you and you cannot have a messed up schema. But things get already difficult if you want to map to your custom object from an existing database. ORM's can be a fast road to hell here. Also where high performance is required ORM's are probably not an option. The fastest NHibernate can get compared to ADO is I think around 30%. But for many scenarios this should be sufficient.elLocohttps://www.blogger.com/profile/04685538094487060639noreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-29423306753308222902011-01-29T09:07:35.133-08:002011-01-29T09:07:35.133-08:00I agree with everything that you said on ORM's...I agree with everything that you said on ORM's. The one additonal point I would bring us is performance. We write highly batch oriented systems and it is hard to tweak and design ORM's to be able to mee that type of needs. <br /><br />My question would be where can I go to find more information on non-ORM solutions. It seems like all of the hype is around ORM's now and no one is talked about writing your own data access layer with the newest patterns and techniquies.<br /><br />I would really like to look into generating the mapping between the data results and my objects while writing my own queries for performance.Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-28347225221584697492010-03-12T09:48:08.093-08:002010-03-12T09:48:08.093-08:00Thanks for the link! I will try it.Thanks for the link! I will try it.elLocohttps://www.blogger.com/profile/04685538094487060639noreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-21752184394849701462010-03-12T01:10:09.252-08:002010-03-12T01:10:09.252-08:00DataObjects??<a href="http://www.x-tensive.com/Products/DO/Default.aspx" rel="nofollow">DataObjects</a>??Anonymousnoreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-84193165917973633372010-02-22T05:26:53.640-08:002010-02-22T05:26:53.640-08:00Maybe we are looking from different angles. My per...Maybe we are looking from different angles. My perspective is from the object side ("how do I get my relational data into *my object*"). I assume your view is from the database side ("how do I get *my relational* data into some object"). In this case all these relations are supported on the relational side, but with out of the box Entity Framework 4 not on the object side. There I can only move a property from entity A to B if there is a 1 : 1 relationship.<br /><br />But <a href="http://blogs.msdn.com/adonet/archive/2009/05/21/poco-in-the-entity-framework-part-1-the-experience.aspx" rel="nofollow">here is what I was basically looking for</a>. It is coming with the POCO support. I'll revise the article accordingly.elLocohttps://www.blogger.com/profile/04685538094487060639noreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-7519417899731320332010-02-19T13:34:31.128-08:002010-02-19T13:34:31.128-08:00I don't know where you are looking for your in...I don't know where you are looking for your information. This is totally supported. Both the poco support and the ability to have many-to-many relationships. Again, if you prefer to use nHibernate, that's fine. I just don't want people to have misinformation. For example, have a look at this URL: <a href="http://msdn.microsoft.com/en-us/library/bb399189(VS.100).aspx" rel="nofollow">http://msdn.microsoft.com/en-us/library/bb399189(VS.100).aspx</a>Daniel Simmonshttp://blogs.msdn.com/dsimmons/noreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-17592756892980234832010-02-17T13:46:05.711-08:002010-02-17T13:46:05.711-08:00I checked with RC and still see no way to map a ta...I checked with RC and still see no way to map a table to a List. <br /><br />Take the following example:<br /><br />You have the tables Order, Customer, OrderCustomer. A classic m : m relationsship between Order and Customer through association table.<br /><br />Now show me a model without an entity OrderCustomer, but a class Order that has a List<Customer>.<br /><br />This is <many-to-many> in NHibernate.<br /><br />Believe me. Entity Framework 4 is DataSet 2.0. It's designed relational or it's an ORM tool without O&M. Compared to NHibernate this is toy class. Microsoft should stop wasting their and our time, and instead contribute a good Linq provider for NHibernate. I am sure once you tried NHibernate you agree to this.elLocohttps://www.blogger.com/profile/04685538094487060639noreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-70771148550490130502010-02-16T22:25:57.927-08:002010-02-16T22:25:57.927-08:00That's good to hear. I tried this in Beta 2 an...That's good to hear. I tried this in Beta 2 and will try again in RC.elLocohttps://www.blogger.com/profile/04685538094487060639noreply@blogger.comtag:blogger.com,1999:blog-8389214606941174691.post-35395197943035677592010-02-16T20:21:49.289-08:002010-02-16T20:21:49.289-08:00If you prefer to use nHibernate, then more power t...If you prefer to use nHibernate, then more power to you, but I don't know where you got the idea that EF4 can only support 1-1 relationships. I just wrote a small program against EF4 RC with exactly the class definitions in your sample, and it works just fine.<br /><br />- DannyDaniel Simmonshttp://blogs.msdn.com/dsimmons/noreply@blogger.com