I discussed this some with dbussink, who maintains DO. One of the problems is that you'd have to be able to convert "?" into the native format, while avoiding ? in Strings. So for instance:
"SELECT * from foo where name=""?"" and id = ?" This is a simple case--it can be a lot trickier than that. One possible solution is to ban the use of literal strings where bind variables are also used. Thoughts? -- Yehuda Jeremy Kemper wrote: > On Fri, Aug 7, 2009 at 10:35 AM, Nate W<nwi...@gmail.com> wrote: > >>>> 2) Any AR changes in the works that would affect this? >>>> >>> Yes, but in a postive way. Miloops' ARel branch at least centralizes >>> all the query generation, hopefully you can leverage some of the >>> tidying he's done to get a head start on your work. >>> >> Cool, I spoke with miloops via email about this and he was >> enthusiastic like me. >> >> What should the next steps be? Should I start putting bind variable >> support into ARel, and then when that's all merged upstream in to AR, >> AR will get bind variables? >> >> Or should I wait until after the merge and look at it then? (I guess >> my real question is: Is ARel going into AR "as-is" or will it be >> changed/refactored significantly?) >> > > As-is. ARel will use bind vars throughout and AR can take advantage. > > Either way, we can attack the problem from both ends. Check out > miloops' rails fork (which will be merging to master in the near > future) and take a look at how relations are built and composed. > > Best, > jeremy > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
