Jeremy Kemper wrote: > I'd start with using bound variables first, though. They're always > beneficial and are a natural stepping stone to prepared statements > which can be added later for those queries which may benefit (many do > not).
From my tests w/ Oracle, all the benefit was in the use of (real, aka database) bind variables. For a while now I've had a working (passes all tests) implementation of AR that uses bind variables for inserts and updates, those being by far the easiest to tweak. Given how widely spread throughout the codebase the selects are, I haven't had the time to think through a reasonable approach there. Though I like what was suggested (by you I think) back in Feb, around the idea of SqlString < String. Has anyone looked into that further? > Are you attending RailsConf this week? Perhaps a group of us could get together to dig into this? --~--~---------~--~----~------------~-------~--~----~ 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 [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
