I haven't been able to get one to work satisfactorily. It is most likely
that you will need to redesign your data structures to accommodate your
context policies - depending on how important the context functionality is
to you. We get results back on over 8 Gig of text documents (stored in long
raw columns in the database) in less than 2.5 seconds on fairly average
hardware. How much data are you searching through? Remember that context
does not actually search through the table, but rather looks up the indexes
created or updated on insert and update. Perhaps you could use a post
insert/update trigger to populate a separate table with just the desired
data in it and apply a context policy to that.
>Is is possible, using column indexes, table joins, or other optimization
>techniques, to get ConText to search through a subset of the rows of a
>text-indexed table instead of the entire table? I have tried several
>things and don't see any improvement in performance.
>Any hints would be greatly appreciated.
> David Schwartz