Unfortunately, it won't change in b1, it might change before the final
release if I can find a better solution. The problem is in the Vocabulary,
not in the Catalog itself. One of the things I'm focusing on is improving
the algorithms that are used for doing globbing.
Chris
- Original
Christopher Petrilli wrote:
Unfortunately, it won't change in b1, it might change before the final
release if I can find a better solution. The problem is in the Vocabulary,
not in the Catalog itself. One of the things I'm focusing on is improving
the algorithms that are used for doing
Michael Bernstein wrote:
Christopher Petrilli wrote:
Unfortunately, it won't change in b1, it might change before the final
release if I can find a better solution. The problem is in the Vocabulary,
not in the Catalog itself. One of the things I'm focusing on is improving
the
Michael Bernstein wrote:
Christopher Petrilli wrote:
Unfortunately, it won't change in b1, it might change before the final
release if I can find a better solution. The problem is in the
Vocabulary,
not in the Catalog itself. One of the things I'm focusing on is
improving
For a similar project (http://mailarchive.activestate.com) we too use a
MSSQL back end, for various reasons similar to Chris. I'm not worried
about
it, once upon a time I tried to stick everying in the ZODB. To me one of
Zope's great strengths is it's portability and connectivity to other
