• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: specifying number of rows to fetch
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: specifying number of rows to fetch


  • Subject: Re: specifying number of rows to fetch
  • From: Ricardo Strausz <email@hidden>
  • Date: Fri, 25 Jun 2004 10:45:34 +0200

On Jun 25, 2004, at 7:01 AM, email@hidden
wrote:

> From: Art Isbell <email@hidden>
> Date: June 25, 2004 12:40:52 AM CEST
> To: WOdev List <email@hidden>
> Subject: Re: specifying number of rows to fetch
>
>
> On Jun 24, 2004, at 11:37 AM, John Spicer wrote:
>
>> I have a front end client I'm writing in objective-c using web
>> services.
>
> 	Any comments about how well this approach is working would be
> appreciated.  Does the Web services communication overhead seem
> reasonable?  I.e., does the response time for a fetch as seen by the
> ObjC client seem similar to that of a WO app?

Furthermore, is it better/easer that Cocoa/EOF?? Please let us know!!!

>
>> I call a function to load the items in a table. I'm only getting the
>> first hundred, and I'm assuming there is a place to tell it to get
>> them all (or the number specified).
>
> 	EOFetchSpecification.setFetchLimit().  The default is no limit, so
> something in your EOF server must be setting the limit to 100.  Or if
> the EOF server is fetching in the EOAccess layer, the fetch loop that
> invokes EOAdaptorChannel.fetchRow() may be limiting the loop iteration
> to 100.
>
> 	Another consideration is the number of fetched objects that a human
> can reasonably process.  Do you really expect your users to examine
> 100+ fetched objects?  That can be quite a load in many cases.  In
> ObjC/EOF apps that I've written way back when, I would first fetch the
> count of objects that match the fetch specification.  If that count
> exceeded a configurable maximum, I would ask the user whether she
> really wants to fetch that many objects suggesting that a tighter
> qualification might be preferable.

This can still be done with something like
[fetchSpecification promptOnLimit:YES];

So it will fetch the first "limit" rows and, if there are more, it will
ask the user if s.he want to fetch more (the options are, if I can
remember, "all", "next 'limit'", "cancel"; just as inside EOModeler).

Dino

>
> Aloha,
> Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.


  • Follow-Ups:
    • Re: specifying number of rows to fetch
      • From: "Goh Keng Boon" <email@hidden>
  • Prev by Date: Re: DTJC runs a client DB
  • Next by Date: [ANN] InSetQualifier - ... WHERE x IN (a, b, c)
  • Previous by thread: Re: specifying number of rows to fetch
  • Next by thread: Re: specifying number of rows to fetch
  • Index(es):
    • Date
    • Thread