Hi Chris
It's not quite that simple, but here are your options:
Use the callback object, generated on the fly, not through a callback:
ThinkingSphinx::RealTime.callback_for(:user).after_save(user)
Or you can essentially take the approach of the implementation within that:
indices = ThinkingSphinx::Configuration.instance.indices_for_references(:user)
indices.each do |index|
ThinkingSphinx::RealTime::Transcriber.new(index).copy user
end
If you're doing this regularly, I guess you could wrap either of those into a
method of your own.
--
Pat
On 15/10/2013, at 1:50 AM, Chris Sturgill <[email protected]> wrote:
> Apart from setting an after_save callback, is there a way to manually force a
> real-time update of a given object? As an example,
>
> user = User.first
>
> Is there a way to trigger an update for the indexed record for the "user"
> object? E.g., user.update_realtime_index.
>
> This is not as useful in the example provided above, but given complex
> relationships it can be easier to manage explicitly rather than worry about
> configuring the appropriate callback chains.
>
> --
> You received this message because you are subscribed to the Google Groups
> "Thinking Sphinx" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> To post to this group, send email to [email protected].
> Visit this group at http://groups.google.com/group/thinking-sphinx.
> For more options, visit https://groups.google.com/groups/opt_out.
--
You received this message because you are subscribed to the Google Groups
"Thinking Sphinx" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/thinking-sphinx.
For more options, visit https://groups.google.com/groups/opt_out.
