Richard Holland wrote: > The dates don't necessarily follow each other. > > The dataset modified date is the last time that someone ran an 'update > all', or the date when the dataset was first created if no updates have > been made yet. > > The dataset configuration modified date was the last time the > configuration changed. > > As an update does not necessarily trigger a configuration change, then > the two dates can end up in reverse order. > > The date to rely on, should you need to make comparisons, would be the > configuration modified date.
That's a shame. I'm trying to cache the dataset configurations as downloading them takes a considerable amount of time. I can't compare the configuration modified dates unless I download the configuration and that somewhat defeats the object of creating the cache. David. -- David Withers School of Computer Science, University of Manchester, Oxford Road, Manchester, M13 9PL, UK. Tel: +44(0)161 275 0145
