On Wednesday 13 May 2009, Adam wrote: > After the lively discussion at RailsConf regarding refactoring > patches for Rails I'd like to raise awareness once more of my patch > to fix the improper inheritance relationship between HMT and HOT > association classes.
I'm in favor of your patch and have commented on the ticket. Still, I think there biggest issues with ActiveRecord is something else: It is basically gluing together bits and pieces of generated and provided SQL without much concept of what it is doing. Try anything interesting involving associations, scopes, and a few joins. You either end up with too many joins between the same tables or duplicate aliases the DBMS is going to complain about. What about those naming conventions when the same table occurs multiple times? ARec needs to take a step back from concrete SQL strings, toward abstract models of the various SQL statements. This (huge) step would allow for better modularity, customizability, and easier expression of programmer intention. I have no idea how to introduce a change such as this as it would surely void backward compatibility. Sigh, only dreaming. Michael -- Michael Schuerig mailto:mich...@schuerig.de http://www.schuerig.de/michael/ --~--~---------~--~----~------------~-------~--~----~ 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-core@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 -~----------~----~----~----~------~----~------~--~---
