Nhibernate basically maps the object layer to your tables. It is extremely flexible, but you still have to be able to map object to tables in some way. I didn't read this through completely, but it looks like the Entity layer is just providing a way to describe that mapping so that it can transform object centric queries (which is what Nhibernate uses) into the underlying sql (which is what Nhibernate does). If their mapping is extremely flexible, I suppose they could get close to iBatis, but it's still probably closer to the Nhibernate sweet spot. In fact, this has been discussed on the Nhiberate forums.
-----Original Message----- From: Bob Hanson [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 31, 2007 12:42 PM To: [email protected] Subject: Re: ADO.NET Entity Framework I don't know enough about nHibernate but my understanding is that it enforces certain rules on your database design. That's why I like iBatis. But my interpretation of the MS document is that the Entity Framework is closer to iBatis because it also doesn't force any design rules on your database. LINQ looks interesting because it becomes a general query syntax for any datasource whether a SQL database or some other store. On 1/31/07, Clough, Samuel (USPC.PRG.Atlanta) <[EMAIL PROTECTED]> wrote: > It obviously could have some overlap with iBatis. To me, it's closer to > an Nhibernate competitor. Most iBatis users probable want to control > the SQL or want to be able to map a domain layer that doesn't > necessarily fit neatly into a DB scheme. This will require a schema > that can be modeled in a fairly straightforward way. It requires LINQ > to really work and my initial reaction has been that we don't need to > embed a sql derivative (it looks like a clone of hsql to me if you've > used Hibernate) into the actual language. That's just me though. > > -----Original Message----- > From: Bob Hanson [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 31, 2007 12:20 PM > To: [email protected] > Subject: ADO.NET Entity Framework > > http://msdn2.microsoft.com/en-us/library/aa697427(VS.80).aspx > > Will the ADO.NET Entity framework make iBATIS.NET obsolete? It appears > that it will provide the same type of mapping framework as iBATIS > while also providing tools for mapping and code generation. Throw in > LINQ to Entities and it would seem that MS will provide a framework > that would be equivalent to iBATIS plus LINQ to iBATIS (assuming the > latter was eventually written). > > Thoughts? > -------------------------------------------------------- > > Princeton Retirement Group, Inc - Important Terms > This E-mail is not intended for distribution to, or use by, any person or entity in any location where such distribution or use would be contrary to law or regulation, or which would subject Princeton Retirement Group, Inc. or any affiliate to any registration requirement within such location. > This E-mail may contain privileged or confidential information or may otherwise be protected by work product immunity or other legal rules. No confidentiality or privilege is waived or lost by any mistransmission. Access, copying or re-use of information by non-intended or non-authorized recipients is prohibited. If you are not an intended recipient of this E-mail, please notify the sender, delete it and do not read, act upon, print, disclose, copy, retain or redistribute any portion of this E-mail. > The transmission and content of this E-mail cannot be guaranteed to be secure or error-free. Therefore, we cannot represent that the information in this E-mail is complete, accurate, uncorrupted, timely or free of viruses, and Princeton Retirement Group, Inc. cannot accept any liability for E-mails that have been altered in the course of delivery. Princeton Retirement Group, Inc. reserves the right to monitor, review and retain all electronic communications, including E-mail, traveling through its networks and systems (subject to and in accordance with local laws). If any of your details are incorrect or if you no longer wish to receive mailings such as this by E-mail please contact the sender by reply E-mail. > > -------------------------------------------------------- >
