Hi Jeffrey SphinxHelper isn't used much - beyond setting up the database, but that's just to avoid complaints from the models. It definitely doesn't generate an index file nor run Sphinx. If you need to test against a live Sphinx setup, I'd prefer you used the cucumber features. Add your model to features/support/models/, and a migration - using the old 1.x syntax if you would like me to merge - to features/support/db/ migrations/.
To run a single cucumber feature, you need to regenerate the cucumber.yml file using rake cucumber_defaults, and then use the default profile: cucumber -p default features/whatever.feature To run all the features, the rake tasks features:mysql and features:postgresql are what you need to call. If your system supports both, you can run both at once with 'rake features'. Hope this is helpful - let me know if you get stuck. Cheers -- Pat On 28/02/2009, at 11:28 AM, Jeffrey Chupp wrote: > > I'm trying to make some modifications to Thinking Sphinx, but sadly > can't figure out how to force an index to build in the specs. I'm in > active_record_spec and my model is fine and there are entries in the > db. What code should I add to force the index to build? > > I read the codebase, but it wasn't obvious to me. There's the > SphinxHelper which has an index method, but it isn't used anywhere > that I can find, and I can't grok how I would use it. > > All that I want to do is force an index to build on a single model. > Any advice you can offer would be very helpful. Apologies if this is > covered somewhere that I missed. > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Thinking Sphinx" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/thinking-sphinx?hl=en -~----------~----~----~----~------~----~------~--~---
