On Monday, March 27, 2017 at 5:04:08 PM UTC-7, Aryk Grosz wrote: > > Hi Jeremy, instead of posting a new thread, I thought I would dove-tail > off this one. :) > > Whenever you use join or association_join, do you have to include a > select_all statement? >
If any of the columns overlap, you should probably specify a selection. That is not necessarily via select_all, it could be via select. > If yes, this would be a difference from other ORMs like AR where they will > by default target the main specific table. This is generally a good > default, otherwise columns (like ID) end up conflicting. > Sequel offers the table_select plugin if you would like the default selection to be the model's table. I'm considering making that the default in Sequel 5. > Maybe there is a default or something I'm missing, but basically whenever > I do a join I have to also be thinking if I need the select_all. > > I'm guessing this was intended by design? > The default is to use the dataset provided selection. If you don't specify a selection in the model's dataset, then you end up with *, as that is Sequel's default selection. 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 https://groups.google.com/group/sequel-talk. For more options, visit https://groups.google.com/d/optout.
