I don't know what is your UI (JSP, Swing or JasperReports), but I'll
share my experience:
1) Yes, OJB could handle collections as large as 660.000 records (yes,
660Krecords!!!) - using proxies, of course, and sometimes tweaking some
-Xmx, -Xms and other memory options of the VM. I've used it to
manipulate (search and update) postal codes of my country, and found no
problems at all.
2) When using Swing, for large amount of objects, never use JList - it
try to read every object even if it not being shown; Use JTable instead,
that will read only records shown. If your logic allow, use pagination +
proxy. Work like a charm, and will not "kill" your database...
3) Until JasperReport 1.0, was not possible to deal with very large
amount of data. Since 1.0 there is an option, but I never used, and I
don't even know if works. It's not an OJB problem, but a JasperReports
problem (I expect this been solved since JR 1.0).
4) Never try to render and HTML page with more than 100~250 records: the
problem is your client machine (every browser I've tryied - read IE and
FireFox - have problems with large pages), except your client machines
run Linux and have 1Gb RAM ;-)
Best regards,
Edson Richter
Jakob Braeuchi escreveu:
hi laran,
yo can use a proxy for the whole collection:
http://db.apache.org/ojb/docu/guides/basic-technique.html#Using+a+Single+Proxy+for+a+Whole+Collection
jakob
Laran Evans schrieb:
I have a parent object which owns a collection. The objects in the
collection are mapped in ojb. However, the parent may own 10K or more
of the child objects. Thus, the collection may be 10K elements or more
in size. The child objects each hold references to other mapped
objects. Clearly loading the initial parent object would blow up the
system. So, I'm trying to figure out a way to load the parent object
but load the collection in batches.
Is there any mechanism in OJB to do anything similar to this? Does OJB
do anything inherently, or can it be made to do so with customization
to handle really large collections?
I can write custom Query calls if needed. I'd like to stick with as
simple a solution as possible.
- laran
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
