Re: Strange catalog behavior on Plone 5.1

Hey.

It's pretty unlikely changes in the ZODB would result in a single test
failure in a Plone catalog.

I'd say the more likely culprit is the inclusion of collective.indexing.
I think its code got merged into the CMF/Plone catalog tools for Plone
5.1.

Maybe you could try to get a hold of the index queue and peek into it,
and see what that gives you
(https://github.com/zopefoundation/Products.CMFCore/blob/2.3/Products/CMFCore/indexing.py).

HTH,
Hanno

On Fri, Jul 21, 2017, at 17:16, Héctor Velarde wrote:
> TL;DR catalog results differ in Plone 5.1 (ZODB 5.2.4) from Plone 5.0 
> (ZODB 3.10.7).
> 
> excuse me about cross posting but after I opened this thread I realized 
> this list could be a better place to find an answer:
> 
> https://community.plone.org/t/strange-catalog-behavior-on-plone-5-1/4582?u=hvelarde

-- 
You received this message because you are subscribed to the Google Groups "zodb" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.