[pmwiki-users] Trouble with .pageindex when too much _new_ data to index (+ sqlite)

Petko Yotov 5ko at 5ko.fr
Sat Feb 28 17:51:04 CST 2015

The error you describe comes from the SQLite recipe and could appear if 
the database cannot correctly return the page records, which can 
possibly happen when there is too much data or not enough time/memory.

Is there any particular reason to use the still experimental SQLite 
PageStore class, largely untested for large volume or large traffic 
wikis? Current versions of the filesystems are quite fast and, with a 
recipe like PerGroupSubdirectories, PmWiki should be able to handle a 
large number of small pages.

Probably even on a cheap shared hosting. Or, if you require more 
dedicated power, but cannot configure, secure and maintain a VPS/DS, 
there are "Performance" shared hosting plans 
(http://www.ovh.com/fr/hebergement-web/offres-performance.xml or 
for example).

You appear to import your pages from an existing database. It may be 
possible to use some of the recipes listed here:


On 2015-02-27 22:38, ABClf wrote:
> i'm still (desesperatly) fighting with pmwiki
> last try was to post new pmwiki, sqlite recipe, setup config, and post
> sqlite database (100mo) somewhere on my website (1&1 shared host) ; 
> then
> ask for Site.Reindex page.
> I'm getting this sqlite recipe related error at the very beginning 
> (just
> after count was done ; nothing created in wiki.d) :
> Fatal error: Call to a member function fetchAll() on a non-object in
> /homepages/18/d269604285/htdocs/dev4/cookbook/sqlite.php on line 403

More information about the pmwiki-users mailing list