<div dir="ltr"><div class="gmail_default" style="font-family:'courier new',monospace">Main reason I'm playing with sqlite recipe is because I have a lot of data I wish to publish using pmwiki rather than another program.</div><div class="gmail_default" style="font-family:'courier new',monospace">I have Words (70k) and Quotes (100k), and Sources (3k).</div><div class="gmail_default" style="font-family:'courier new',monospace">Words group is the most important ; every Word should have a pagelist getting and formatting the linked Quotes. </div><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace">Posting separatly each data in a dedicated (short or very short) store would be very handy, with a pair of links for connecting the data, although it would make a large amount of pages. Acceptable for database, but not easy to handle (back up, massive search and replace, etc.) for text files. The huge pageindex might be an issue as well. Not sure the pagelist would still work.</div><div class="gmail_default" style="font-family:'courier new',monospace">(Last tests with sqlite were not positive at the end, reaching the limit, yet I might have better result with text files).</div><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace">Then I'm going to play now with txt files (using xml page store recipe). </div><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace">As for PerGroupSubdirectories, no known issue to set up something like that (up to about 12000 files max in a folder) ? :</div><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace"><div class="gmail_default"># XML PageStore</div><div class="gmail_default">$EnablePageStoreXML = 1;<br></div><div class="gmail_default">include_once('cookbook/XMLPageStore.php');</div><div class="gmail_default">$WikiDir = new XMLPageStore('wiki.d/{$Group}/{$Name1}/{$FullName}');</div><div class="gmail_default"><br></div><div class="gmail_default">Well, no, I dont want to rely on low used recipes for main task. </div><div class="gmail_default"><br></div><div class="gmail_default">Thank you,</div></div><div class="gmail_default" style="font-family:'courier new',monospace">Gilles.</div><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_default" style="font-family:'courier new',monospace"><br></div><div class="gmail_extra"><br><div class="gmail_quote">2015-03-01 0:51 GMT+01:00 Petko Yotov <span dir="ltr"><<a href="mailto:5ko@5ko.fr" target="_blank">5ko@5ko.fr</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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.<br>
<br>
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.<br>
<br>
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 (<a href="http://www.ovh.com/fr/hebergement-web/offres-performance.xml" target="_blank">http://www.ovh.com/fr/<u></u>hebergement-web/offres-<u></u>performance.xml</a> or <a href="http://www.1and1.fr/hebergement-web?__lf=Static&linkOrigin=serveur-infogere&linkId=hd.subnav.hosting.hebergement-web" target="_blank">http://www.1and1.fr/<u></u>hebergement-web?__lf=Static&<u></u>linkOrigin=serveur-infogere&<u></u>linkId=hd.subnav.hosting.<u></u>hebergement-web</a> for example).<br>
<br>
You appear to import your pages from an existing database. It may be possible to use some of the recipes listed here:<br>
<a href="http://www.pmwiki.org/wiki/Cookbook/CompareDatabaseRecipes" target="_blank">http://www.pmwiki.org/wiki/<u></u>Cookbook/<u></u>CompareDatabaseRecipes</a><span><font color="#888888"><br>
<br>
Petko</font></span><span><br>
<br>
On 2015-02-27 22:38, ABClf wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>
i'm still (desesperatly) fighting with pmwiki<br></span><span>
last try was to post new pmwiki, sqlite recipe, setup config, and post<br>
sqlite database (100mo) somewhere on my website (1&1 shared host) ; then<br>
ask for Site.Reindex page.<br>
<br>
I'm getting this sqlite recipe related error at the very beginning (just<br>
after count was done ; nothing created in wiki.d) :<br>
<br></span><span>
Fatal error: Call to a member function fetchAll() on a non-object in<br>
/homepages/18/d269604285/<u></u>htdocs/dev4/cookbook/sqlite.<u></u>php on line 403<br>
</span></blockquote>
<br><div><div>
<br>
______________________________<u></u>_________________<br>
pmwiki-users mailing list<br>
<a href="mailto:pmwiki-users@pmichaud.com" target="_blank">pmwiki-users@pmichaud.com</a><br>
<a href="http://www.pmichaud.com/mailman/listinfo/pmwiki-users" target="_blank">http://www.pmichaud.com/<u></u>mailman/listinfo/pmwiki-users</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div><div><br></div><div>---------------------------------------</div>| A | de la langue française<br>| B | <a href="http://www.languefrancaise.net/" target="_blank">http://www.languefrancaise.net</a><br>| C | <a href="mailto:languefrancaise@gmail.com" target="_blank">languefrancaise@gmail.com</a><br>---------------------------------------<div> @bobmonamour</div><div>---------------------------------------</div></div>
</div></div>