-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 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. cheers, Richard David Withers wrote: > The modified dates for the datasets in the compara_mart_homology_42 mart > don't match up with the modified dates of the dataset configurations. > > e.g. compara_agam_lafr_orthologs : dataset modified 2006-11-19 17:44:33, > dataset configuration modified 2006-11-19 17:23:18. > > Am I right in thinking that these two dates should match up? > > David. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFFrmI04C5LeMEKA/QRAn1ZAKCQk4e58buiRIC3FwWeSPw+2h36KACgnZ1w r/mFk4qc8f4Eo5gL4egYB2s= =Xvif -----END PGP SIGNATURE-----
