I believe most of applications will have the following requirement:
1. Screen which fetches data from databases such as ORACLE
2. The screen has a limitation to show maximum number of records, let's say
20.
3. The fetched rows exceed > 20. So the main screen shows a pointers for
page 1 , 2 , 3 ...
To code this the developer has to write a cache function for each screen
and mechanism to store and retrieve. JDBC functions to skip result set rows
may not work since the query may be returning rows in random order. Also
the cache has to be designed in such a way it does not eat too much memory.
One of my projects , we did a slow cache with small memory foot print. The
main query will retrieve ROWIDs(ORACLE) and cache , each page hit will
slice through ROWIDs cache and user ROWIDs to retrieve from ORACLE ( WHERE
ROWID IN ( 'xx.xx.xx.xx','yy.yyy.yy.yy') ).
If turbine includes a base class for the mulit-page screen it will very
useful. Is anyone out there has done any similar work??
Thanks a lot
ganesan
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
