David Balmain wrote:
> On 9/19/06, David Sheldon <[EMAIL PROTECTED]> wrote:
>> so cannot define their field infos. Previously I was able to just
>> specify the properties when adding that field to the document.
>>
>> David
>
> I'm assuming the matriculation field is always going to be a number.
> It won't change at a later date. So you can just set up the field
> whenever you use it for the first time.
I've considered this. I use aaf, and this requires the model that
describes what fields are allowed on objects to have access to the index
models indexer, this isn't too bad. The only problem is when the index
is created by something like rebuild_index, which needs to be extended
to create all the extra fields.
I don't want to add the fields to fields_for_ferret, as that would mean
calling #{fieldname}_for_ferret for each possible property, rather than
taking the properties defined on that user, and adding them.
Would the fields_for_ferret solution be the correct way, somehow
populating this out of the database and then overriding the
foo_to_ferret methods to look in a cache?
This was really easy with the old API. It seems a shame that it is so
hard now.
David
--
Posted via http://www.ruby-forum.com/.
_______________________________________________
Ferret-talk mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/ferret-talk
