To bump this thread...
http://www.continuousthinking.com/2007/3/15/refactoring-activerecord-base
Since AR can change so rapidly, I am planning on working on the
majority my patch over the weekend so I can propose changes before to
much else changes. After the first patch is done I will submit it to
those here on core, to receive some feedback, suggestions and
criticism, and also to give me some time to reflect. After that I'm
planning on revising the patch one or two more times before submitting
for a final submission to AR itself.
I'm game for remote pairing as well as I believe two heads are better
then one, and that it will be most crucial to keep these changes as
simple and as clean as possible. Any core dev or AR hacker interested?
Zach
On Mar 2, 7:58 am, "Isak Hansen" <[EMAIL PROTECTED]> wrote:
> On 2/24/07, Anthony Eden <[EMAIL PROTECTED]> wrote:
>
>
>
> > Following up on Koz's suggestion to discuss how plugin developers are
> > monkey patching AR, I'd like to share some of things my coworkers and
> > I have done.
>
> What do you all think of adding a new key to find's option hash, for
> adapter specific extensions, optimizer hints and similar? Unrecognized
> keys would just be ignored.
>
> E.g.:
> find(:all, :conditions => query, :ext => { :prepare => false, :db2 =>
> {:prepare => true}, :mxyzptlk => false })
>
> Isak
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
