Re: Caching with EO

Gino,

It sounds to me like it wouldn't be necessary to cache full EO  
objects to provide a lookup table in memory for lon/lat info.  I  
would probably fetch this data and create a dictionary (or array of  
dictionaries) containing the lookup table.  I would also make that a  
lazy cache, so it is only gets loaded into memory on the first  
request.  Of course you would need to reset the cache if the lon/lat  
information in the database changes, so build-in a reset operation  
for your lazy "in-memory" cache.

This is a guess of course since there's only enough information  
provided in to post to guess at your design requirements.

On Jan 4, 2007, at 10:01 AM, Gino Pacitti wrote:

> Hi All
>
> Can anybody offer a little help as to a strategy for record access.
>
> I have a table with 28000 records which hold lon lat information to  
> which I have to query during a repetition.
>
> For each record in a repetition I need to access a different table  
> and pull lon lat for each postcode - this could be up to 100  
> simultaneous requests by individual users.
>
> Is it best to set the entity to Cache in Memory and collect objects  
> or is it better to collect raw rows?
>
> Any help and advise would be appreciated..
>
> Gino
>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Webobjects-dev mailing list      ([email protected])
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/webobjects-dev/robertwalker1% 
> 40mac.com
>
> This email sent to [email protected]

--
Robert Walker
[email protected]

_______________________________________________
WebObjects-dev mailing list
[email protected]
http://www.omnigroup.com/mailman/listinfo/webobjects-dev