Thanks for the concern. Right now I’m kinda stuck though, the discussion seems to have halted and I don’t know why, or whether the core team is interested. I spoke to some people on #rubyonrails and they said that I shouldn’t try to send patches and that I should write a plugin instead, and that that’s how people contribute to Rails – by creating plugins instead of patches. But since my changes dive deep into ActiveRecord internals I’d rather submit a patch. I was told “who cares, it’s Ruby, patching methods is easy” but I don’t agree with that. Just because something is easy and possible doesn’t mean that it should be done.
The people on rubyonrails-core also seem to be somewhat skeptical about the advantages of prepared statements. Right now I’m looking for benchmarks and hard evidence that prove the use of prepared statements is advantageous, but so far I can’t seem to find any. Many people outside the Ruby on Rails world say that prepared statements are faster and that one should use them, but I’m really having a hard time finding hard evidence to back up that claim. If you know any, I would greatly appreciate it if you could tell me.

Also, Hongli, you’re doing some awesome work with ActiveRecord and other core issues which I’d hate to see slow down for a side project such as this.