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
<*> 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/
