We don't provide a direct way to do what you want, but ERXEOAccessUtilities._rawRowsForSQLExpression is close. You should be able to take that code and down inside of the loop, you could probably manually add snapshots to EODatabase and then trigger faults for them one-by-one. When you're done with each row, you can explicitly forget the objects you faulted and the snapshots should get refcounted to zero and go away. It might be useful to add a method that does this.
ms
On Mar 22, 2010, at 5:47 PM, Lon Varscsak wrote: I was trying to keep the memory footprint as small as possible and fetching all of the PKs seemed to be "too much". I'm thinking more along the lines of when you'd fetch stuff directly from JDBC and just process one result at a time after having executed a sql statement.
-Lon On Mon, Mar 22, 2010 at 2:42 PM, Chuck Hill <email@hidden> wrote:
On Mar 22, 2010, at 2:23 PM, Lon Varscsak wrote:
I have a bunch of rows I need to do processing on and it would be create to fetch EOs one by one from the result set instead of all of them at once. I know this is possible at the EOAccess level, but I didn't know if there was a better/simpler way to do it (including something in WOnder).
Any thoughts?
Chuck
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their overall knowledge of WebObjects or who are trying to solve specific problems.
http://www.global-village.net/products/practical_webobjects
|