[Javtools-poolmngr] Chunking

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

In response to Isabelle
"I'm also not clear on how you see the technical implementation of chunking.
Let's say the query is "select * from authors where first_name like 'ISA%'.
How are you going to tell the database to return only N rows? I don't think
you can. "
We can do that by limiting the records in the SQL queries.
The reson i though about "chuncking" was (I have discussed thsi with stefaan
but this isnt a part of the mailing list) so id state my reasons for
documentation and for every 1 to comment :
The basic design behind this pool manager is using a limited no of physical
connections to execute transactions(statments) lined up on a  stack and
executed serially.
Now a large query (Query generating a large amount of resultSet) would hold
the physical connection for a long time deprieving execution of otehr
queries on the stack.
Stefaan came up witha  solution as having a pool of physical connection
internally for the pool manager.
So we had other free connections even if there was a large query being
executed .
So do we still need to worry about chunking or we cud stop worying abt it
affecting the performance ?
Plz comment.
There was a dicsussion on the lines of caching query results sets well this
is a no-no i feel.
- Amit