Hi folks,
A question about a probably quite common issue in n-tier apps...
Suppose I have a java client - session bean - entity bean(s) - DB.
Suppose the data we're dealing with consist of huge lists (of names, or
whatever) PK:ed on a running integer. Could contain millions of entries.
The data could conceptually be seen as consisting of interval groups, where
all entries in an interval belong together and are often retrieved and processed
together.
The client user wants to perform a bunch of filtered searches on a list:
"Show items 1-1000 and 1000-1500, show all names containing an 'a', ..."
I'm wondering about two things here:
1) Is there some "common/best practice" for deciding how and when to retrieve
the data from the DB to the client? I'm particularly interested in hearing
of experiences comparing session bean -> DB via direkt SQL (stored
procedures, etc) vs session bean -> entity beans (hopefully cached).
2) Is there some common/best practice of representing such massive amounts of
data in a client? What about in the database? Could the interval group
property of the data be exploited in some clever way?
As for 1), the natural answer seems to me to be to fetch each data interval as
the user requests it. The downside to this might be that the server will need to
go through the entire data list each time a filter operation is requested, which
is why I'm asking for good ideas.
As for 2), I don't mean graphically (though ideas for that are welcome too :-)
as much as structurally, especially in the case where the data can be seen as a
group of non-overlapping intervals (items 1-1000 and 2000-10000 and ...).
We can assume that the entity beans have exclusive write access to the DB.
Regards,
Jonas
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
