Noted, I pondered this actually but decided against fixing it now - its probably less overhead than you think since the catalogs table is tiny today (mine is 16 MB on a 20,000 node collection) - but I guess its worth fixing esp. if we want to store historical catalogs. Looks like the fix is is trivial enough either way. Patch forth-coming.