ok, a little sum up.
To understand what happens, here is the setup:
Page called Clients, container for every client.
every client got his unique number written to the title.
The client template itself contains a set of round about 35 fields.
I imported a set of data via CSV import Module.
This set is provided by a client of mine who needs a new Intranet Solution.
His client Database contains exactly 15987 entries.
Every entry is one client and so every client is a page.
As you can see in the screenshot, PW provides a automatic pagination.
To handle this amount of data pagination is definitly not the best way.
To edit and manage some clients you could use the built in search engine in the backend.
Maybe I want to edit clients with the name Richard.
I just pick my Clients Name field, type Richard in the Search box, et voila.
What also could be interesting, is the performance of PW.
Lets have a look:
<? $pages->find('template=kunde'); ?>
All clients in one PageArray gives me the following : Page generated in 33.5099 seconds.
<? $pages->find('template=kunde,limit=50'); ?>
Results in : Page generated in 0.0376 seconds.
Rendering those sets of data doesnt affect our render time much. The following:
<? foreach($pages->find('template=kunde,limit=50') as $client): ?>
<p>Number: <?= $client->title ?></p>
<? endforeach ?>
Results in: Page generated in 0.0462 seconds.
Conclusion:
At a certain point you dont have to worry about how to order pages, instead you have to worry about how to catch your pageArrays as efficient as possible.
Managing large amounts of data is somewhat to think about at the very beginning.
I´m handling the clients in a tree like this: Home/Database/Clients/
Hope this was helpful