On Wed, Jan 08, 2003 at 05:34:06PM +0100, Matthias Andree wrote: > IMHO, the db_setvalue can be killed and every code be switched to change > db_setvalue_and_* -- it's the db-storing that figures if the timestamp > needs to be saved. why dont we just call it db_setvalue (instead of db_setvalue_and_date)? -- gram