[Zope] ZCTextIndex - prefix wildcards not supported?

[Andreas Jung]

ZCTextIndex does not support left truncation (as far as I know). The reason 
is that
an efficient implementation requires a second internal BTree structure 
which means
more memory consumption.

-aj

--On Donnerstag, 20. November 2003 13:55 Uhr -0500 Small Business Services 
<toolkit at magma.ca> wrote:

> Thanks for the alternative Andreas, however we currently have ZCTextIndex
> installed in a ZCatalog that has about 700,000 entries (about 3Gb of data)
> and would prefer to stay with ZCTextIndex (unless there are some other
> advantages to move to TextIndexNG2 given our situation?).
>
> Is there any way/interest in having this '*term' type of wildcard
> searching built into ZCTextIndex?
>
> jh
>
>
>> TextIndexNG2 supports this feature.
>>
>> -aj
>>
>> --On Donnerstag, 20. November 2003 12:38 Uhr -0500 Small Business
>> Services <toolkit at magma.ca> wrote:
>>
>> > Why are wildcards '?' and '*' not supported at the beginning of search
>> > terms in ZCTextIndex?  It would be very useful to search for terms
>> > using '*someterm'.
>> >
>> > In the cvs for ZCTextIndex, Lexicon.py
>> > (http://cvs.zope.org/Products/ZCTextIndex/Lexicon.py?annotate=1.17.10.
>> > 2)
>> >
>> > the code raises an exception for wildcards at the beginning of search
>> > terms (see line 113) and a related comment says"
>> >
>> > 111                                  # The pattern starts with a
> globbing
>> > character. 112                                  # This is too
>> > efficient, so we raise an exception.
>> >
>> > Why is this 'too efficient"?
>> >
>> >
>> > Jonathan
>
>
>
> _______________________________________________
> Zope maillist  -  Zope at zope.org
> http://mail.zope.org/mailman/listinfo/zope
> **   No cross posts or HTML encoding!  **
> (Related lists -
>  http://mail.zope.org/mailman/listinfo/zope-announce
>  http://mail.zope.org/mailman/listinfo/zope-dev )