Re: [ts] Delayed raising of connection errors in Rails 3

[Timo Virkkala]

It's a documented feature. Just add :populate => true to your searches
to have TS populate the search results (and therefore run into errors)
right away.

http://pat.github.com/ts/en/common_issues.html#exceptions

-T-

On Fri, Oct 12, 2012 at 7:05 PM, Jason Fox <ja...@readmedia.com> wrote:
> I noticed an odd behavior with thinking_sphinx (2.0.10) and Rails 3.1. If
> the sphinx server is down, an exception is not thrown until the results
> collection is accessed. However, in the console, an exception is thrown
> when the search is executed. So, I find myself having to "tickle" the
> results collection, e.g., @results.total_count, in the controller to get it
> throw the connection exception (if it's down) in the controller. Anyone
> else notice this?
>
> Thanks,
> Jason
>
> --
> You received this message because you are subscribed to the Google Groups
> "Thinking Sphinx" group.
> To view this discussion on the web visit
> https://groups.google.com/d/msg/thinking-sphinx/-/n1KREWk4dg8J.
> To post to this group, send email to thinkin...@googlegroups.com.
> To unsubscribe from this group, send email to
> thinking-sphi...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/thinking-sphinx?hl=en.

[Pat Allan]

Hi Jason

Searches are lazily loaded (like Arel in Rails 3), so it's only because the console renders the search as the output that it gets populated. The controller isn't displaying the search object, hence it's only in the view that an error gets raised (unless you are making use of search results in a controller).

Hope that helps clarify things a little.

Cheers

--
Pat

On 14/10/2012, at 12:51 PM, Jason Fox wrote:

> Actually, that didn't fully answer my question. I was/am wondering why an exception thrown when the search is executed in the console vs. accessed in the controller?

> To view this discussion on the web visit https://groups.google.com/d/msg/thinking-sphinx/-/98et4zIaitMJ.