Hi Courtenay You're right that TS now supports Octopus (and other custom db adapters), however I'm not sure of the best approach to switch between read and write options.
Can't think of any reasonably elegant options off the top of my head at the moment, I'm afraid. The quick fix is to edit the configuration file manually. Is there a reason why TS can't always use the read/write master? Could set up a secondary environment, duplicating production with slightly different db settings and run the TS rake tasks via that environment instead? Let me know what path you end up going down. Cheers -- Pat On 29/03/2011, at 7:53 AM, court3nay wrote: > It appears as though using Octopus with TS is possible. Is this being > used in the wild? > > - See also this thread; > http://groups.google.com/group/thinking-sphinx/browse_thread/thread/b8489a58e1e5d0c1/69fcef665c2058a8?lnk=gst&q=octopus#69fcef665c2058a8 > > - I noticed this specifically mentioning octopus: > http://freelancing-god.github.com/ts/en/common_issues.html#other_adapters > > However, we use a delayed delta index, which runs an UPDATE ALL before > indexing. I don't think that's going to work, since our slave db is > readonly. How do people do this normally? > > -- > 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. > -- 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.
