From 2fecb273b3da3fb3fabaf1d8f321fd8b55a89a68 Mon Sep 17 00:00:00 2001 From: dsyer Date: Sat, 1 Aug 2009 20:00:59 +0000 Subject: [PATCH] Correct database intro in reader/writers section --- .../docbook/reference/readersAndWriters.xml | 22 +++++++------------ 1 file changed, 8 insertions(+), 14 deletions(-) diff --git a/src/site/docbook/reference/readersAndWriters.xml b/src/site/docbook/reference/readersAndWriters.xml index 0b846283a..644f6bd61 100644 --- a/src/site/docbook/reference/readersAndWriters.xml +++ b/src/site/docbook/reference/readersAndWriters.xml @@ -1716,20 +1716,14 @@ staxItemWriter.write(trade);
Database - Like most enterprise application styles, a database is the central - storage mechanism for batch. However, batch differs from other application - styles due to the sheer size of the datasets with which the system must - work. The Spring Core JdbcTemplate illustrates this - problem well. If you use JdbcTemplate with a - RowMapper, the RowMapper - will be called once for every result returned from the provided query. - This causes few issues in scenarios where the dataset is small, but the - large datasets often necessary for batch processing would cause any JVM to - crash quickly. If the SQL statement returns 1 million rows, the - RowMapper will be called 1 million times, holding - all returned results in memory until all rows have been read. Spring Batch - provides two types of solutions for this problem: Cursor and Paging - database ItemReaders. + Like most enterprise application styles, a database is the + central storage mechanism for batch. However, batch differs from + other application styles due to the sheer size of the datasets + with which the system must work. If a SQL statement returns 1 + million rows, the result set probably holds all returned results + in memory until all rows have been read. Spring Batch provides two + types of solutions for this problem: Cursor and Paging database + ItemReaders.
Cursor Based ItemReaders