I wouldnt really say IBATIS vs an O/R mapper is comparing apples and oranges They are both Data Abstraction layers...
A quick comparison: MyGenerations dOOdads vs IBATIS Setup of dOOdads: http://www.mygenerationsoftware.com/dOOdads/dOOdads.aspx Examples of dOOdads: http://www.mygenerationsoftware.com/dOOdads/VBNet_MasterSample.aspx Steps for setup are steps which need to be done to switch between databases. Realisticly regenerating the d00dad classes will take about 10 - 20 minutes including setup time + copying files to the directory's One needs to compile the project afterwards, and then it's all set. >From what I've heard most O/R mapper solutions have some sort of code generation setup to do about the same. So switching databases isn't to hard. dOOdad syntax: // Load and Save Employees emps = new Employees(); if(emps.LoadByPrimaryKey(42)) { emps.LastName = "Just Got Married"; emps.Save(); } // Add a new record Employees emps = new Employees(); emps.AddNew(); emps.FirstName = "Mr."; emps.LastName = "dOOdad"; emps.Save(); // After save the identity column is already here for me. int i = emps.EmployeeID; Syntax of IBATIS: http://www.ibatis.com/common/example.html Address address = new Address(); address.setId(15); address.setDescription("Bob's Comic Book Store"); address.setStreet ("16 Somestreet"); ... sqlMap.insert ("insertAddress", address); When you look at this you see that both need to have classes generated... In other words if anything changes then it's a matter of regenerating these classes again. Too me personally d00dads wins in elegance. Especially when you take into account that dOOdads requires 0 handwritten sql. Another more known O/R mapper also has config data in XML files. Also looks like there isn't a recompile needed: http://jira.nhibernate.org/confluence/display/NH/Quick+Start+Guide ----- Original Message ----- From: "Charles Carroll" <[EMAIL PROTECTED]> To: <[email protected]> Sent: Friday, April 08, 2005 8:07 AM Subject: Re: [AspNetAnyQuestionIsOk] IBatis: 1 app supporting ANY database > > But of course they are apples and oranges. > > O/R mappers attempt to solve 100s of problems. > > IBatis allows very easy migration from 1 DB to another or from SQL to > Sprocs without recompiling code and in many cases the person making > the XML files that do the DBmapping need not muck with code. > > ORMs are something different. You could probably even use an ORM on > top of Ibatis. But changing databases (SQLserver to Oracle or Access > or mySQL) is a huge deal with most ORMs and most apps -- heck even > changing from ad-hoc SQL to Sprocs on same DB -- is a big deal without > IUBatis. And trivial with IBatis -- even people who are not mucking > with the code can throw ina few XML files to allow the code to > support another DB entirely. > > One thing also is IBATIS athe DB could be changed by just changing > config files and not rewriting or regenerating the app. This is HUGE. > > On Apr 6, 2005 4:22 PM, Mischa Kroon <[EMAIL PROTECTED]> wrote: >> I'm not really a fan of IBATIS. >> >> Personally I would go with an O/R mapper for easy database independence. >> Both have their advantages and disadvantages tough. > > > > Yahoo! Groups Links > > > > > > > > > -- > No virus found in this incoming message. > Checked by AVG Anti-Virus. > Version: 7.0.308 / Virus Database: 266.9.3 - Release Date: 4/5/2005 > > Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/AspNetAnyQuestionIsOk/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
