They are stored non-indexed fields. In my case I wanted to have some
stock data in searchable index. This is not top priority, as I can
really have a second index or a database and do lookups by :id.
If I were to wish for something in coming Ferret, I'd wish "stability".
I am getting seg_faults every other time I am doing this:
def self.internal_field_values(fieldname)
term_enum = @@reader.terms_from(Ferret::Index::Term.new(fieldname,
""));
out = []
while term_enum.term and (term_enum.term.field == fieldname) # seg
faults here
out << term_enum.term.text
break unless term_enum.next?
end
out
end
> As for just updating the stored-unindexed fields, I'll have to think
> about it. It'll add a bit of complexity to the merge process which I'm
> not to keen on. But it is certainly possible. Sergei, what type of
> field is it that you need to update? And to everyone else on the list,
> is this a common action? That is, do you often need to update
> non-indexed fields?
>
> Cheers,
> Dave
--
Posted via http://www.ruby-forum.com/.
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk
