"R. David Murray" wrote:
> On Wed, 24 May 2000, Chris Withers wrote:
> > This is weird... the bit of code in question was:
> > lib/python/SearchIndex/Lexicon.py line 132:
> [...]
> > Now Michel's patch was to change this to:
> > else:
> > self.counter = self.counter + 1
> >
On Wed, 24 May 2000, Chris Withers wrote:
> This is weird... the bit of code in question was:
> lib/python/SearchIndex/Lexicon.py line 132:
[...]
> Now Michel's patch was to change this to:
> else:
> self.counter = self.counter + 1
> self._lexicon[intern(word)] = se
Michel Pelletier wrote:
[snip]
> ???
>
> I'm looking into this right now...
How's this going?
I'm going to release Squishdot 0.4.0 today with a "Don't use SiteAccess"
and "You may have to hit Re-Index a few times" warning but I'd like to
know whether I have bug hunting to do or if ZCatalog h
Michel Pelletier wrote:
>
> I'm looking into this right now...
>
Many thanks :-)
As you may have gathered from my posts, I've been having a bit of a
ZCatalog/SiteAccess (not to mention MIME) nightmare today...
...I took a day off work to try and get Squishdot 0.4.0 out and have
spent the day
Chris Withers wrote:
>
> Itamar Shtull-Trauring wrote:
> > Last I heard, this bug fix did NOT fix the key-error problem. We are still
> > getting lots of them (but it may have been fixed since in CVS. Michel?)
>
> This is weird... the bit of code in question was:
> lib/python/SearchIndex/Lexic
Itamar Shtull-Trauring wrote:
> You're using 2.1.6? That's something different. The KeyErrors bug only
> appeared in CVS ZCatalog - the partial searching version. So it must be
> something else - and for all I know this bug is fixed in CVS.
Yeah, this is happening on 2.1.6 as part of Squishdot
Chris Withers wrote:
> I'm not even going to try and guess which is right, all I know is that I
> haven't made either change yet and I'm getting an unacceptable number of
> incorrect search results in stock 2.1.6 and would like to sort it out...
You're using 2.1.6? That's something different.
Itamar Shtull-Trauring wrote:
> Last I heard, this bug fix did NOT fix the key-error problem. We are still
> getting lots of them (but it may have been fixed since in CVS. Michel?)
This is weird... the bit of code in question was:
lib/python/SearchIndex/Lexicon.py line 132:
else:
Itamar Shtull-Trauring wrote:
>
> "R. David Murray" wrote:
>
> > It had better be . It's also a one line fix to Lexicon.py.
> > Mike posted a note explaining the fix and how to retrofit it into
> > an existing site (you have to clear and rebuild the Lexicon, so
> > it becomes a little more than
"R. David Murray" wrote:
> It had better be . It's also a one line fix to Lexicon.py.
> Mike posted a note explaining the fix and how to retrofit it into
> an existing site (you have to clear and rebuild the Lexicon, so
> it becomes a little more than a one line fix). If you can't find
> the me
On Tue, 23 May 2000, Chris Withers wrote:
> The message is the one I linked :-)
Ah, I'm used to the pipermail archive links, and didn't recognize it
as a mailing list link. I should read more carefully!
--RDM
___
Zope-Dev maillist - [EMAIL PROTECT
"R. David Murray" wrote:
> http://zope.nipltd.com/public/lists/dev-archive.nsf/ByKey/C15EB30D0FAF1057
> If you can't find
> the message in the mailing list archives, I can probably did out
> a copy I saved somewhere...
The message is the one I linked :-)
cheers,
Chris
On Tue, 23 May 2000, Chris Withers wrote:
> Would this bug:
> http://zope.nipltd.com/public/lists/dev-archive.nsf/ByKey/C15EB30D0FAF1057
> "[Zope-dev] The Mysterious Key Error and Unrelated Searc Result Bug"
>
> be the reason why I occasionally get incorrect search results (ie: an
> object is re
Michel Pelletier wrote:
[snip stuff on BTree, intSet and PersistentMapping]
> Now you can add these to the InterfaceWiki. ;)
Done... not sure if they're in the right place though...
I'm having problems with ZCatalog.
Would this bug:
http://zope.nipltd.com/public/lists/dev-archive.nsf/ByKey/C1
14 matches
Mail list logo
