Problem is that once you get past simple relationships, it becomes impractical to try to do automatically. If it were simple enough to derive without a manual declaration, you'd think Rails would've gone with that approach.
By requiring it to be done manually on the simple stuff, it becomes second habit and you avoid the nightmare of trying to describe how to use it for complicated cases to people with no prior exposure to the concept. At least, that's my take on it. On Thursday, July 17, 2014 4:25:14 PM UTC-6, Quiliro Ordóñez Baca wrote: > > > > El jue 17 jul 2014 16:47:17 ECT, kevinpfromnm escribió: > > I haven't done much with it but it seems like it's informing rails of > > the other side of the relationship which is mostly useful for avoiding > > extra DB calls and in rare cases, out of date models. > > > > Say you have a post, which has many comments. You load post with all > > comments. Without the inverse of, if you call post from within a > > comment, it makes a new DB call to load post because rails doesn't > > know that it already has the appropriate information. > > > > I saw an example, where the parent was changed but the child still had > > old info. It seemed rather contrived, but I suppose someone might run > > into problems with it. > > Thank you for the info. Shouldn't this be incorporated into Hobo > instead of the user needing to include it in every relationship? > > -- > Saludos libres, > Quiliro Ordóñez > 600 8579 > > -- You received this message because you are subscribed to the Google Groups "Hobo Users" 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/hobousers. For more options, visit https://groups.google.com/d/optout.
