Hi! On Tue, Jan 09, 2007 at 09:47:03PM -0800, Seth J. Morabito wrote: > Hi everyone, > [..] > > IF the locking is leading to corruption problems, one thing that would > really help is if we didn't update the index on every write. We're not > searching on the image view counter, so this might end up being more of > an acts_as_ferret question than a ferret question (i.e., it'd be nice > to tell acts_as_ferret not to reindex the model if we're not updating an > attribute we search on!).
if you're on aaf trunk, this is possible: model_instance.disable_ferret # will disable ferret for the next save model_instance.save or model_instance.disable_ferret do # ferret is disabled for all saves model_instance.save # occuring inside the block end > But that aside, has anyone else encountered problems with heavy > writing? Yes, we've had the very same errors in an application not using aaf. Moveing all the indexing into a single backgroundrb process. Since then everything is fine. I have a drb indexing feature for aaf in the works, too. cheers, Jens -- webit! Gesellschaft für neue Medien mbH www.webit.de Dipl.-Wirtschaftsingenieur Jens Krämer [EMAIL PROTECTED] Schnorrstraße 76 Tel +49 351 46766 0 D-01069 Dresden Fax +49 351 46766 66 _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
