Andreas Jung wrote:
I think the software MG from the book Managing Gigabytes is GPLed and
currently
released as mg-1.21. Walking through the TOC of the book, it seems to be a
very detailed
sources about text processing and gives very much informations about
different indexes types.
But I
Casey Duncan wrote:
I'm not sure I want to store the indexes in the ZODB, just index ZODB data at
a low level.
Ah, okay, and yes, in that case, I am in complete agreement ;-)
(the level I'm aiming at is just to be able to index python objects, I'll leave
plugging that into the ZODB
Dario Lopez-Kästen wrote:
Anyway. In case you were wondering what the previous email meant, there's
the
actual meaning d8)
I'm sure Andy's got a point, but we haven't got the context of those points.
Is he complaining about the change in UserFolder API in Zope 2.5?
cheers,
Chris
On Thu, 29 Nov 2001, Chris Withers wrote:
I would rather avoid having to use a relational database unless I have to.
Perhaps the index pluggability could be made to support different backends
(like FileStorage et al does).
Yeah, unfortunately, the difficult bit is combining queries:
Yikes, it was pointed out to me that I typed amk instead of akm.
Though I knew it was Andrew Milton and not Andrew Kuchling, I mixed up
the letters. (In fact, as I was typing it, I was thinking wow, that
looks like Andrew Kuchling's monogram.)
--Paul
Paul Everitt wrote:
Whew, that
Chris Withers wrote:
Toby Dickenson wrote:
FileStorage is 'damn fast', so almost anything is going to be slower.
Indeed, until it runs out of RAM for its indexes ;-)
I wish you would finish testing the change I made for you.
It should reduce the memory consumption by an order of
I found ZODBC bug at max_rows.
file name: db.py
line: 230
Current version is getting all rows regardless of
max_rows.
Fixed version is getting rows until rows are smaller than
max_rows.
Current version:
while status==SQL_SUCCESS:
.
r.append(rd)
A K Milton wrote:
a) The change to manage_* seems to be completely arbitrary, since we already
had _do* methods that meant you didn't have to call manage_users with
fake submit buttons. So what is the point of having manage_ ?
They were added in response to this fishbowl proposal:
Steve Alexander wrote:
In summary:
I want to make sure that things are no worse in Zope 2.5 final than in
Zope 2.5. Any breakage caused by this API change is a bug, and needs to
be sorted out by Zope 2.5 final.
That should have read:
I want to make sure that the user management
Jim Fulton wrote:
Chris Withers wrote:
Toby Dickenson wrote:
FileStorage is 'damn fast', so almost anything is going to be slower.
Indeed, until it runs out of RAM for its indexes ;-)
I wish you would finish testing the change I made for you.
Sorry, to be clear, my comment
a) The change to manage_* seems to be completely arbitrary,
since we already
had _do* methods that meant you didn't have to call manage_users with
fake submit buttons. So what is the point of having manage_ ?
They were added in response to this fishbowl proposal:
Sorry to post here.
I posted last week on the zope list about what appears to be a new/strange security
related problem in 2.4.3
I thought it was a problem in LdapUserFolder, but jens spent more time debugging than
I did and he feels it's somewhere in the Zope security machinery.
12 matches
Mail list logo
