lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Leo Galambos <>
Subject RE: custom scoring api questions
Date Thu, 02 Jan 2003 21:59:24 GMT
> It's not a bad thought. We're using Oracle and usually would just do a
> SQL query and let Oracle indices take care of the searching. However:
> 1. One of the fields is a clob with >16k of text per entry. We're using
> Oracle's Context, which has proven unreliable and slow.

right, you would parse it to tokens. it could be done by many OS projects 
(i.e. mnoGoSearch) which use RDBMS as backend. It will be faster solution 
for you, I think.

> search on a normalized data structure. Each parent row may have 10-100
> child rows.There may be up to 200,000 parent rows. There may be 60 query
> terms to look for in the child rows. In my inherited codebase, the query
> does 60 joins against the child table for each parent. Needless to say,
> the web page times out before the search is done. Our users are

It sounds like a bug in DB design IMHO.


To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message