Am 19.09.2007 um 05:19 schrieb Chuck Hill:
This, or a related issue can be triggered by firing a large (many
members) back pointing relationship. Sometimes for efficiency,
these are best managed manually and not modeled as a relationship.
You should always model every relationship. You
Hi,
I have recently solved an out of memory problem in a list page by
using a batching display group that just fetches one page worth of
records at a time.
Now I find that creating an object from that page is once again
trying to fetch every record in the data table prior to allowing me
Well, I figured out the problem.
In Practical WebObjects on page 44 Chuck and Sacha recommend as one
possibility moving the LOB data into a related entity. They say that
This allows you to avoid faulting in the LOB until you need it.
When I fetch my entity, the LOB table is included, not
This, or a related issue can be triggered by firing a large (many
members) back pointing relationship. Sometimes for efficiency, these
are best managed manually and not modeled as a relationship.
Chuck
On Sep 18, 2007, at 2:57 PM, David Holt wrote:
Well, I figured out the problem.
In
