Starting Monday I'll be working for myself and one of the things I'm looking forward to is working on ActiveRecord more. I've written and released some ActiveRecord extensions/plugins [0] and as well as posted some thoughts on ActiveRecord's modularity [1]. With this in mind I want to work up a patch to refactor how ActiveRecord itself handles queries.
Alot of what I'd like to do is very similar to my approach with better finder support in ActiveRecord::Extensions [1] Since now is the time that alot of changes are happening for Rails 2.0... what's the core groups feedback on making query support for ActiveRecord more modular. Do you see the current AR implementation limiting what AR can do since anytime someone needs to add functionality they have to write a plugin which overrides AR core methods? In short I think AR would get alot of benefits if AR included things like declarative style registration of query support. register GenericQuerySupport, :adapters => :all This way someone can easily register special functionality for MySQL, PostgreSQL, MS SQL, Oracle, etc, and release the plugin without overriding AR. They can just call: ActiveRecord::Base.register PostgreSQLRegexpSupport, :adapters=>:postgresql Thoughts? Zach 0 - http://www.continuousthinking.com/tags/arext 1 - http://www.rubyinside.com/advent2006/17-extendingar.html --~--~---------~--~----~------------~-------~--~----~ 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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
