Without knowing your app, I would suggest to create a combined Query
and then you could store the result with cfindex like:

<cfindex action="update" query="qry" collection="add" key="id"
body="id,title,customvalues" category="myadd" categoryTree="1">

The body would be a list of the fieldnames with a unique key.

The other option could be to have separate queries and then for each
resultset you have a <cfindex> like above, and each cfindex has the
same categorytree!

Thus this, help you better?

Kind Regards,
Nitai

On Fri, Sep 25, 2009 at 9:57 PM, Jason King <[email protected]> wrote:
> Ok, so for instance. We have a classified ad application. Each ad requires
> approx 2-3 tables, a core table, details table, location table.. About 80%
> of each table needs to be searchable. Would I create a single index that
> combines all searcheable fields from all tables? That way lucerne only has
> to parse a single index?
>
>
>
>
> On Fri, Sep 25, 2009 at 1:28 PM, Nitai @ Razuna <[email protected]> wrote:
>>
>> They are not that big. Our DB contains a couple of GB and the Lucene
>> file is just a fraction of it.
>>
>> On Fri, Sep 25, 2009 at 8:19 PM, Jason King <[email protected]>
>> wrote:
>> > Am I wrong to think that the index files for the search could be as big
>> > as
>> > the DB files themselves?
>> > >
>> >
>>
>>
>>
>> --
>> Razuna SaaS On-Demand - Hosted Digital Asset Management Solution
>> http://www.razuna.com/
>>
>> Razuna - Open Source Digital Asset Management
>> http://www.razuna.org/
>>
>> Follow us on Twitter
>> http://twitter.com/sixsigns
>> >>
>



-- 
Razuna SaaS On-Demand - Hosted Digital Asset Management Solution
http://www.razuna.com/

Razuna - Open Source Digital Asset Management
http://www.razuna.org/

Follow us on Twitter
http://twitter.com/sixsigns

--~--~---------~--~----~------------~-------~--~----~
Open BlueDragon Public Mailing List
 http://groups.google.com/group/openbd?hl=en
 official site @ http://www.openbluedragon.org/

!! save a network - trim replies before posting !!
-~----------~----~----~----~------~----~------~--~---

Reply via email to