Only in the form of constant complaints from oracle users :). But from memory oracle does a lot of work when it creates a prepared statement including running the optimiser and getting a query plan for execution. I believe this is quife expensive so doing it once makes things fast. Perhaps an oracle user can chime in here?
On Sunday, April 12, 2009, Hongli Lai <[email protected]> wrote: > > On Apr 11, 11:59 pm, Michael Koziarski <[email protected]> wrote: >> The difference here depends on the database and how its optimiser >> works. I believe the last time we looked at it there was no >> difference on mysql, slightly negative impact on postgres (the >> optimiser didn't know the types of the variables so couldn't use >> indexes) and *major* improvements to oracle. So it's not a straight >> up and down win, however if you wanted to spend some time tidying up >> the query generation to make this possible, that'd be neat. > > Interesting. At the time I only tested with MySQL and PostgreSQL. > > Any published data about performance improvements in Oracle? > > > -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
