On Fri, Oct 13, 2006 at 09:40:23AM +0900, David Balmain wrote: > On 10/13/06, Jeff Gortatowsky <[EMAIL PROTECTED]> wrote: [..] > > Also, was there any way to stop AaF from trying to create a new > > index with all the existing model data? I was surprised when after > > creating and updating one model object in the Rails Console, AaF > > took off trying to index all 8 million rows of the underlying table!
aaf always tries to create the index if it doesn't exist yet. The whole point about aaf is to keep the index in sync with your database. Therefore it is necessary to add all existing records to a newly created index. Although it would be easy to add an option to suppress the indexing of existing data, I don't think this is useful, because you'll end up with an index only containing new or updated records, but not those that already existed at index creation time. I can't imagine this is what you want ;-) To keep the index creation from happening when the index is accessed the first time from your app (could be a search, or some update/create operation), you can build up the index from the console, i.e. RAILS_ENV=production script/console >> Model.rebuild_index 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
