Roman Rokytskyy wrote:

>>>The idea is that one should be able to search for 'CAINE' and
>>>match all the 'CAIN', 'KANE', 'CANE', 'KINE' equivalents, and then
>>>search on 'BIRTH' or 'ISLE OF MAN' to further restrict the result
>>>set.
>
> This can be easily satisfied with a UDF that computes the SOUNDEX
> code. Full-text search is primarily about phrases. So, if we take your
> description as requirement - we don't need full-text search.

Or grouping of a number of key words within a document?
'JAMES LESTER CAINE BIRTH' Provide a result set and allow processing on
the result set.

>>I have an assortment of databases and documents forming the results
>>of searching for family history information. Ideally the whole lot
>>needs to be massaged into a consistent database with links to each
>>piece of source information relating to each 'person' record, but
>>just searching the data is a start.
>
> What prevents you from creating a specific database and use Lucene in
> parallel to your database? If I understand your requirements
> correctly, you do not really need an integration of full-text search
> and SQL (which I assume should be used to specify queries).

Currently the requirements are quite simple, but if the 1Gb of documents
that I currently have access to in house are indexed properly, then ANY
sort of full-text search should be possible without rescanning all that
data. Yes I can carry on using external libraries to achieve the same
result, but I'd be happier if the engine was controlling more of it. I
still think that this is a combination of internal and external
functions, but the 'systems tables' need to be usable by anybody as
extensions are developed.

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services