Hi Josef, There are good reasons for keeping APIs footprint small and not adding unnecessary public methods, even if they may be easy to implement. So before talking implementation, maybe making a strong case for why this `ordered?` would be a good addition to the Rails API would help your idea get traction.
So like others I must ask: why do you need this? I tried to think of some use cases, but all of them could be achieved by, instead of trying to add a default order after your query is mostly built, by setting the default order first, then reordering later when the code calls for it. This way, if your conditional logic did not reorder, the default order makes it through. Also, I am not convinced the implementation, or even the definition of this `ordered?` method is that easy. It may be for the simple single model query case. But now throw in some relations, joins and includes, some of these ordered, some others not. What should `ordered?` return? -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-core/e8e90ad4-ae77-4e23-85dd-ddcf0ed39239%40googlegroups.com.
