Re: Raw Rows versus EOs
Re: Raw Rows versus EOs
- Subject: Re: Raw Rows versus EOs
- From: Robert Walker <email@hidden>
- Date: Wed, 2 Feb 2005 17:17:25 -0500
There's another issue to consider when using WODisplayGroup having to
do with backtracking. Try this on a display group managing batches:
1. Navigate forward a few pages.
2. Hit the browser's back button.
3. Perform an action (such as edit) an any displayed row.
You will notice that the wrong EO is selected for the action.
I don't know if this is really a bug in WODisplayGroup, or if there is
simply no way to avoid this problem via HTTP requests and backtracking.
On Feb 2, 2005, at 1:04 PM, Kieran Kelleher wrote:
Thanks Colin and Chuck for the insight.
Chuck, if you don't use WODisplayGroups at all, do you use a homegrown
batch navigator for big NSArrays?
-Kieran
On Feb 2, 2005, at 12:37 PM, Chuck Hill wrote:
I'd also start questioning the design and usage of my application if
I was showing the user 10,000 or 100,000 of anything to select from.
Who is going to wade though all that? It seems to me like it is just
wasting resources and the user's time. Maybe this is an artifact of
using display groups? Personally, I never use them preferring to
manage an NSArray myself.
As Colin said, for raw rows, a lot depends on what you are planning
on doing with them. If you are only displaying a few attributes and
don't need any of the logic in the EOs and will only turn a few into
real EOs, then around 1,000 might be a good guide for raw row
fetches. Perhaps less if you are really tight on memory. If you
need most of the attributes, or need logic from the EOs to display,
or will end up turning most of them into EOs, there is little benefit
to starting from a raw row fetch.
Chuck
On Feb 1, 2005, at 2:15 PM, Colin Clark wrote:
Hi Kieran,
On Monday, January 31, 2005, at 11:10 AM, Kieran Kelleher wrote:
What's the best practice or recommended approximate threshold at
which you fetch raw rows for display groups instead of EO's? 100
... 1,000 .... 10,000 ..... 100,000 ?
I know this isn't the answer you're looking for, but it totally
depends on the specifics of your application. It depends on how
large the EO is, how often these objects are fetched, how you
actually use the EOs once they've been fetched, and other
domain-specific requirements.
Basically, the best practice is to use raw row fetches when it
becomes too time-consuming or resource intensive to fetch complete
EOs given the requirements of your application.
Does that help at all?
Colin
---
Colin Clark
Dynamic Web and Database Development Lead,
Resource Centre for Academic Technology,
University of Toronto
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
--
Practical WebObjects - a book for intermediate WebObjects developers
who want to increase their overall knowledge of WebObjects, or those
who are trying to solve specific application development problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
email@hidden
This email sent to email@hidden
--
Robert Walker
Bennett Technology Group
(770) 957-1866 Ext: 790
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden