Submitted by : simon at: 2005-02-04T19:31:13+00:00 (16 years ago)
Name :
Category : Severity : Status :
Optional subject :  
Optional comment :

We could simplify code and perhaps improve consistency of search behaviour by dropping support for no-catalog wikis and requiring that a catalog be present.

This raises the issue of how to set one up when it's needed. Ideally the user would have to do nothing.

Related to #1145.

update --simon, Fri, 06 Apr 2007 21:13:45 +0000 reply

betabug and I discussed this. It's time to bite the bullet and say a zwiki always has a catalog, period. We will auto-create one in the upgrade() method if needed, just like the outline object. This will take care of new wikis, single-page wikis, and upgraded wikis, although you could see a very slow (minutes) first page view after upgrading a large wiki.

implemented for 0.60 --simon, Fri, 06 Apr 2007 21:57:52 +0000 reply

Severity: wishlist => normal Status: open => closed

Zwiki now auto-creates a catalog in the wiki folder when needed, similar to the "outline" page hierarchy cache.

Here's a situation where this could be problematic: indexing a large wiki can be an expensive operation (taking minutes, using extra memory), and this will be initiated simply by the first page view after upgrading from Zwiki <0.60.

Code can now assume a catalog is present, though it's still a good idea to use Zwiki's pages() search api when appropriate. We can probably simplify a number of things later based on this, after it has had some production testing.

implemented for 0.60 --simon, Fri, 06 Apr 2007 22:10:53 +0000 reply

Another possible problem: imagine upgrading a busy public wiki, even with loads of memory. Multiple requests may try to set up the catalog, tying up the whole zope server and possibly conflicting with each other and screwing up the whole operation. Real-world reports and better ideas welcome.