On 2/25/07, Michael Koziarski <[EMAIL PROTECTED]> wrote: > > I think this is one of the messier areas of the current query > generation code. Because we do replace_bind_variables on each of the > [string, val, val] blocks we're passed, we can't use prepared > statements. Now while this doesn't matter for mysql or postgresql, > in the big commercial databases it makes a huge difference. >
Hey buddy, please do elaborate on that last sentence. Postgres doesn't benefit from prepared statements? What kind of performance improvements have you (not) been seeing? What kind of data/queries? As you mention mysql and postgres in the same breath I'm thinking this is just FUD, but if there's really something here I'm eager to know. Thanks, 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 -~----------~----~----~----~------~----~------~--~---
