Thanks Jeremy- Apologies for the picture attachments, didn't know that was not good.
We've adopted set_graph_aliases already- they are awesome btw :) We've tested out the generated SQL and it looks good :) Cheers, Dean On Saturday, 7 June 2014 00:48:53 UTC+10, Jeremy Evans wrote: > > On Thursday, June 5, 2014 11:36:32 PM UTC-7, Dean Cornish wrote: >> >> Ignore last :) >> >> We've figured it out: >> >> Application.eager_graph(:irs => [:releases,:deployments => [:build] >>> ]).select( >> >> >> Is there a better way of doing this? it seems like it going to get rather >> messy quite soon :) >> > > No. How much more are you going to try to add into a single query? If > you think that's messy, you should look at the resulting SQL. > > Also, as I mentioned above, you can't (or at least shouldn't) use select > with eager_graph, you should use set_graph_aliases. > > If possible, I recommend using eager instead of eager_graph, as it should > perform much better for the example you are giving. > > And please, no more posts with pictures of your schema. Use some sort of > text based format for it. > > Thanks, > Jeremy > -- You received this message because you are subscribed to the Google Groups "sequel-talk" 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/sequel-talk. For more options, visit https://groups.google.com/d/optout.
