Re: Fetching in a thread
Kieran Kelleher <[email protected]>
| Newsgroups | gmane.comp.web.webobjects.devel |
|---|---|
| Message-ID | <[email protected]> |
Some alternative options might be worth considering (1 or more may just solve the fetch speed issue into the < 0.5ms range)..... 1) Have you looked at the actual slow queries hitting the db and looked at table index or indices to speed up those fetches? 2) "Fetching and sorting" .... are you using a FetchSpec that includes EOSortOrderings so the data comes back sorted from the fetch? 3) Is the table underlying the entity optimally designed .... no blobs, excessive attributes/fields that are only required when editing or viewing the single EO? 4) Fetching raw-rows for display lists and hydrating those into EOs as the user selects them individually for viewing/editing can be effective in large row fetches 5) If the SQL is just not optimal, then are you able to produce hand- written SQL that selects the records faster than the SQL produced by EOF? If so, that can be used in the FetchSpec hints. HTH, Kieran On May 2, 2007, at 11:18 PM, Michael Deninger wrote: > Fetching and sorting those records can take several (2-10) seconds > and otherwise interrupts their workflow _______________________________________________ WebObjects-dev mailing list [email protected] http://www.omnigroup.com/mailman/listinfo/webobjects-dev