Re: finding all Java classes in a project

Sreenivasa Viswanadha wrote:
> 
>> Err ;) I don't think it is a task for MDR, it would place too heavy 
>> integrity constraints on the database <-> source mapper (delay on 
>> database update < some-small-value, ...).
> 
> 
> I disagree. I think this is one of the basic functions that MDR should 
> provide. First of all
> my understanding is that MDR is just a cache, not a database. So I don't 
> see why it should
> update the database/cache.
> 
Although MDR is logically a cache, it is essentially a database for 
objects and their relationships. Some people use databases for caching 
data which are hard (but possible) to obtain.

Update is necessary if the function needs to return accurate results, 
rather than those from most-recent update, or partial results from an 
update running in background right now.

-Svata