There's a ton of magic in active record as is. If you have ideas on a big change like the one you are suggesting, you should fork active record and get it working to get feedback. After that it's worth discussing.
If you really want to help here, take a look at open issues tagged with active record and see if you can solve them. AR has the most issues open by far. — Richard Schneeman On Sat, May 17, 2014 at 6:38 PM, Lawrence Wu <lawre...@lawrencewu.me> wrote: > I'd like to deprecate methods like includes and eager_load in Rails since I > think it is possible to automatically detect when they are needed. Ideally > the developer could know very little about how databases work and still get > very efficient queries using just the ORM. What do other people think? > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to rubyonrails-core+unsubscr...@googlegroups.com. > To post to this group, send email to rubyonrails-core@googlegroups.com. > Visit this group at http://groups.google.com/group/rubyonrails-core. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-core+unsubscr...@googlegroups.com. To post to this group, send email to rubyonrails-core@googlegroups.com. Visit this group at http://groups.google.com/group/rubyonrails-core. For more options, visit https://groups.google.com/d/optout.
