Let me try another approach of how I answer this:

SQL is a set processing langage. You select a set, update a set where, etc., SQL engines are optimised for this for many decades. (See set theory, unions, intersections, SQL P&T, etc.) In general, row by row processing is discuraged when working w/ SQL dbs and is not optimal.

So... row by row processing, or cursor processing is more ORM. ORM attemnts to do SQL optimizing on the Java side, by storing rows as objects and computing. ORM is row aware and ads complexity to Java layer.

Set processing is more SQL Mapping. Native Optimization from the SQL engine is leveraged. SQL mapping is not aware of rows, it's aware of a set of results that may be cached should somone else required identical result set.



Your Roomity Broadband Community <http://roomity.com/demo.jsp>

cell: 917 825 3035 in DFW
email: netsql at roomity.com

Reply via email to