I'd probably drop the hobo_index call and just build the array manually if you're doing all that already as pagination (the one thing hobo_index is bringing to the table) is probably going to need to be custom built too.
On Jul 19, 12:10 pm, Chris Apolzon <[email protected]> wrote: > Hi all, > I'm trying to display an odd sort of index page. I'm cherry picking > three different data sets from one parent model (Manuscripts). > Because of the way I need to pull data out, I can't use a fancy > group_by scope call. I thought I'd be there if I was able to write > each query as a named scope. However, when I try to concatenate or > operate on the three results in any way to push them into one object, > the scope turns into an array and hobo_index is apparently incapable > of handling an array for its block; it needs a scope. > > So I'm wondering if > a.) Anyone knows how to concatenate scopes and coerce them back > into scopes > b.) Anyone knows how to pass an array into hobo_index > c.) How to pass multiple collections into hobo_index > > To further complicate matters, I need the three queries to be separate > in some way. My current solution was to grab the three queries, and > then create a scoped result by collecting all the ids from my three > queries. However, then I have no way of telling where one section > stops and the next begins in the view. > > Thanks for any help :) -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers?hl=en.
