You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
Presently, the feature restricts users to a single search operation per index. However, in scenarios involving a Single Table Inheritance model within Rails, there arises a need to execute multiple searches within the same index, each with distinct filter criteria.
The crux of the matter lies in the structure of our input data, which revolves around objects. As such, attempting to define the same key more than once becomes an issue. For example:
I'm not opposed to it. As it stands, I still think I prefer having a hash so each search has something that can identify it. Using that algolia example I would prefer:
Description
Presently, the feature restricts users to a single search operation per index. However, in scenarios involving a Single Table Inheritance model within Rails, there arises a need to execute multiple searches within the same index, each with distinct filter criteria.
The crux of the matter lies in the structure of our input data, which revolves around objects. As such, attempting to define the same key more than once becomes an issue. For example:
In this instance the first query would be overwritten by the second and result in only one query.
In the ideal world we'd want to emulate what Algolia's rails implementation for multiple_queries
The text was updated successfully, but these errors were encountered: