[Javtools-poolmngr] Requirement for Chunking

[Amit D. <ami...@ra...>]

Quoting Stefaan : 
"This could maybe proof a usefull utility in the db pool mngr.
In my opinion the use of resultset chunks is a bit obsolete. 
Since the most restrictions will be execute in a where clause of the
statement
which reflect the size of the resultset.
Why do you want to provide this utility and to what perpuse for the user?"

Steefan,
       Since we are going to have a thread based architecture.
How about this scenario :
 User specifies a chunk of 5 :
 We get the first chunk of 5 (using limit in the WHERE clause)
 return it to the user.
 (Assuming that the user now process this chunk)
 Meanwhile we have the next chunk ready in the thread.
 The user requests the next chunk and we give it to the user ,we already
have it ready.
 I am not to sure how the objects are gonna collaborate but we wud geta
clear picture during the technical design n object model.
Data retrieved is directly proportional to time.
So less data retrieved on each query and the same query being executed
repeatedly (which cud be a prepared query) Vs large data being retrieved in
a single query.
Also this might give rise to the issue of a timeout (If we have such a
criteria).The user might have 100000 records and request them in chunks of 5
, chunking doesnt seem good now.
Your opinion.
Regards,
Amit