DBA, I'm not sure that would be the right things to do. The #count/#size/#length has been a documented feature of AR for as long as I can remember changing it on any scope does not sound like a good idea to me.
- Ken > Hello and thanks for the feedback. > > foca, thanks for the clarification. I did know about the differences > between .size and .count but I didn't remember about .length. > > However, despite length returning the needed results (potentially with > an extra query), I find it misleading to have AR execute a COUNT query > on both .count and .size that ignores the current scope, deliberately > expressed by the developer. > > In that regard, I think Jeremy is right appointed Sequel behavior is > more in line with what the average developer - like myself - would > expect AR to return. > > I'm not too familiar with AR codebase, but I'll try and check how hard > it would be to modify .count and .size, making them take into account > the current scope. > > Thanks, > DBA -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to rubyonrails-c...@googlegroups.com. To unsubscribe from this group, send email to rubyonrails-core+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en.
