[Catalog-sig] start on static generation, and caching - apache config.
renesd at gmail.com
Sun Jul 8 07:36:21 CEST 2007
It's less work to just look up to see when the last change was.
Rather than make another table and store it - duplicating the data.
On 7/8/07, "Martin v. Löwis" <martin at v.loewis.de> wrote:
> > Next up I'm going to put a few functions into store.py. Ones to check
> > if a release has changed since a given date. Also one to see if any
> > changes at all have happened since a given date.
> Is this really necessary? I think it would be sufficient to have a table
> of name,version pairs that list the releases that have changed. This
> table is filled on modification, and cleared by the regeneration.
More information about the Catalog-SIG