RE: ADO.NET Entity Framework

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

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.

RE: ADO.NET Entity Framework

Nhibernate can support compound keys and legacy table structures, but it is difficult to configure and encourages but does not enforce certain styles of database design. -Original Message- From: Bob Hanson [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 31, 2007 12:42 PM To:

Re: ADO.NET Entity Framework

Bob and others Trust me, the Entity Framework won't even come close to iBATIS. Here is some information I can share (because it's already public): 1) The entity framework is a HUGE abstraction on top of your database. It's literally another layer. Databases have various layers including

RE: Storing Connection Strings in the connectionStrings in .config files

Hi Gilles: Thanks for offering this option. The compiler complains about DomSqlMapBuilder.Properties not providing a getter. I've confirmed there is no getter in my 1.5.1 code base or the Subversion tip (http://svn.apache.org/repos/asf/ibatis/trunk/cs/mapper/IBatisNet.DataMa