ibatis-user-java mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fabio Insaccanebbia <finsaccaneb...@gmail.com>
Subject Re: iBATIS 2.1.5 is out (despite the website)
Date Tue, 19 Jul 2005 14:56:19 GMT
IMHO, there could be a couple of reasons (not technical and not even
so "strong") that could suggest to add RowSet support.

1 - a RowSet support could simplify the migration from a non-iBatis
framework (my situation)
      1st step - substitute the RowSet/ResultSet homemade framework
with iBatis, gaining immediately better cache support and SQL dynamic
      2nd step - introduce gradually the objects instead of RowSet
2 - there is a pattern called "Data Transfer Rowset" that in some
situations, could be used side-by-side with DAO. If I can't implement
it with iBatis, but I still need it in an application that is mostly
DAO based, I should create another "query catalog" and another "cache
management" (or introduce a DIY Rowset with a List of Maps.. so why
don't build it in iBatis? :-).

As a said, quite "weak" reasons.. still, I'd find RowSet support useful  :-) 


2005/7/19, Clinton Begin <clinton.begin@gmail.com>:
>  Abdullah,
>  I'm still not sure why we'd ever support RowSets.  The whole point of
> iBATIS is to move data between the database and objects.  If you're using a
> RowSet, you don't have any objects to map to, so what would be the
> advantage?  I suppose iBATIS still has a simpler API, is that enough to make
> RowSet support worthwhile?
>  Cheers,
>  Clinton

View raw message