This issue isn't the fault of AS at all, but rather of Rails. But I wonder, could ActiveScaffold possibly include some automatic fixes/workarounds for AS-enabled application?
My application was running OK on rails 3.x, but in 4.x the behavior of ActiveRecord changed and my application became broken due to https://github.com/rails/rails/issues/5701. I even was forced to disable all ordering in default scopes… :( When I asked (https://github.com/rails/rails/issues/5701#issuecomment-30564717) rails developers about detection this situation and automatically adding needed column to the select list, they replied that it would be too much "magic" in rails to autodetect this and fix the generated SQL query. Now I ask you, what do you think about it? May the AS have this "magic"? What could you advice for those, who like me, needs preserving ordering in related models' default_scopes? Is there any relatively simple way to do this with AS? -- Andrey Korobkov -- You received this message because you are subscribed to the Google Groups "ActiveScaffold : Ruby on Rails Gem" 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/activescaffold. For more options, visit https://groups.google.com/d/optout.
