Well, theoretically, yes. The logical syntax allows such, but after it
didn't work when I tried, the Lucene FAQ says:
Leading wildcards (e.g. /*ook/) are *not* supported by the QueryParser
by default. As of Lucene 2.1, they can be enabled by calling
QueryParser.setAllowLeadingWildcard( true )
Troy,
I am excited about this kind of search capability. This is great work.
I have a question. Will this solution also cover searching for a morph
value for any lemma? It might look like:
morph:*@mor1
instead of
morph:lem1@mor1
In other words, if I want to find all the masculine, singular
Hey Chris,
A relational database will not contribute more to a solution than what
we have available in lucene. What I failed to get across in my last
email, due to too much caffeine, was that a verse's declension data by
itself is useless without being attached to the lemma which each morph
