[pmwiki-users] PageLists of database contents

[Martin Fick]

--- "Patrick R. Michaud" <pmichaud at pobox.com> wrote:
> The key to making this more efficient will be to
> reduce the overall number of "pages" (records) that
> MakePageList has to perform  its searches on.   I'm 
> thinking the best approach to this will
> be for us to provide either (1) options to
> ListPages() and ls() or (2) alternate methods 
> entirely so that we can tell a 
> PageStore/DataStore object "we want the names of
> 'pages' that might match these criteria" as opposed 
> to "give me a list of all pages".  Then we can 
> optimize things quite a bit.

You probably know my thougths on this: yes, yes, yes. 
More "Searching" should be done at the pagestore level
so that optimizations can be implemented easily (and
past on to DBs potentially.  With this, it seems like
the page-index should move into the pagestore instead
of the pagelist script.  
 
> I'm also needing to re-think a few of PmWiki's
> internals here, especially the $PCache array.  
> PmWiki uses $PCache in a large number of places to 
> try to avoid doing much in the way of
> "redundant" I/O, but it's been done haphazardly
> without any real overarching design. 

Yes, yes, attributes should also be done at the
pagestore level... this migh break a lot of recipes?

> I wasn't planning to revamp
> $PCache for 2.2... but with the pagelist and page 
> variable changes it's becoming far more relevant,
and
> it might be worth making the change now (as part of
a
> "major release") than to> postpone the pain until 
> later when more modules may be depending on
> the existing haphazard design.

Break it now, pmwiki will be awesome!  Even though it
might break recipes, many of them could be eliminated
or greatly enhanced/simplified with these features
anyway,

-Martin


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com