Re: Oracle - Corba - Client - Server - Pagination

a friend of mine has examined this in an ejb environ (borland 4.5)

afair:

1. cache the rs in a sfsb as 2-dim object array
2. cache the rs in a sfsb as cached rowset
3. cache the rs in a sfsb as xml-string
4. cache the rs in a temporary db-table, fetch by page-no, requires sp's
5. cache the pk's in a sfsb only, fetch by keyset

environ: loadtest with rowsets with about 1000 rows, 200 users, 2 cpus, 500 mb ram, wintel

2. was absolutely the best, very fast
1. and 3. was ok
4. and 5. were really worse, too much db-i/o

"Dsaw" <dsawilson_at_yahoo.ca> wrote in message news:6ee024a2.0209261130.51d4c8df_at_posting.google.com...
> Hi,
>
> I am interested in techniques to handle large Oracle query result sets
> in a client/server environment with Corba (WLE) middleware.
> Since overly large result sets can cause the corba server to hang,
> result xml strings are limited to a certain size. Part of the result
> set may have to be thrown away. It would be preferred if we could
> save the total results of a given query on the server or on the middle
> layer such that the user can page forward and back through data that
> is consistent from the point of time the query was originally made.
> It would also be nice to be able to include a refresh functionality so
> that any new dml activity would show up.
> Is there a way to preserve the total query result set in the database
> to be sent to the client via the middleware in manageable chunks?
> Ideas considered so far include temporary Oracle tables and
> resubmitting the query.
> Is there any way to lock the result set in the database such that it
> can be accessed via other processes through the corba layer?
>
> TIA,
>
> David W.
Received on Thu Sep 26 2002 - 15:07:25 CDT