<table cellspacing="0" cellpadding="0" border="0" ><tr><td valign="top" style="font: inherit;">I should also mention that one of these large collections contains objects with sequential, but not consecutive, numeric ids (timestrings) like some blogs. Users of this database can benefit from the ability to access items added around the same time.<br><br>With or without a catalog, how would one get the next or previous id in such a case?<br><br>--- On <b>Mon, 11/2/09, Andreas Jung <i><lists@zopyx.com></i></b> wrote:<br><blockquote style="border-left: 2px solid rgb(16, 16, 255); margin-left: 5px; padding-left: 5px;"><br>From: Andreas Jung <lists@zopyx.com><br>Subject: Re: [Zope] Large BTreeFolder2 batching/pagination<br>To: "Ken Ara" <feedreader@yahoo.com><br>Cc: zope@zope.org<br>Date: Monday, November 2, 2009, 11:36 AM<br><br><div class="plainMail">Am 02.11.09 11:28, schrieb Ken Ara:<br>> I agree it is hard to imagine, but I am just the
web guy...<br>><br>> If I dare to guess, I would say that what they want to do is improve<br>> access to the information for the users. The two million objects are<br>> strongly interlinked, so this is the navigation system used up to now.<br>> But why not open it up to browsing?<br>><br><br>Because no human can deal in a reasonable way with 500k object..build<br>your *own*<br>custom and working navigation throughout the data records...presenting<br>the ZMI view for BTreefolders to a human is just sick.<br>><br>> For the content team, it might also be nice to use the ZMI or similar<br>> when working with this content.<br>><br>> We have not been successful to create a Catalog of this many objects.<br>> The process seemed to time out after many hours, probably<br>> hardware-bound. Also, the size of the resulting ZODB is of concern,<br>> but we may try again with the Catalog on a mounted database.<br>><br>we
have ZCatalogs with millions of objects..likely you are indexing<br>everything within one big transaction<br>without using savepoints or subtransactions..<br><br><br>><br>-aj<br></div></blockquote></td></tr></table><br>