We have a similar problem (ours is a pair of databases) and ended up keeping a list of changes in the database using database-specific tools (Oracle triggers). If: - your tables have change dates - you can cope with finding deletions the hard way and then repairing the index you could consider retrieving everything changed after the date of last update. If your concern is service continuity, you could consider making the new index in parallel and ~rename~ing it into place. I don't know what Zope has for a rename operation, or what it guarantees. At 16:04 16/08/01 -0700, Kevin Lewandowski wrote:
I have a large SQL database and have successfully cataloged that using the nice howto on zope.org.
The problem is that this database is constantly growing. What's the best way to get new data into the catalog? And how do I update catalog entries when the database changes? This database is maintained by a separate app (not Zope).
I could just drop the catalog and re-create it daily but I was wondering if anyone else has faced this problem before and had any suggestions.
thanks much
-Kevin